Madison Pruet wrote:
> "Art S. Kagel" <kagel@bloomberg.net> wrote in message
> news:43E0E317.2080907@bloomberg.net...
> > bozon wrote:
> > > Art S. Kagel wrote:
> > >
> > >>bozon wrote:
> > >>
> > >>>It would help us. I think it would be a feature that
> would really fit
> > >>>in with the new redundant fault tolerant application
> structure that is
> > >>>popular today.
> > >>
> > >><SNIP>
> > >>
> > >>That raises an additional, related request. That the
> global cursor ID
> be
> > >>sharable across ER replicants. That would allow cost
> free failover to a
> > >>backup server!
> > >>
> >
> > By George I think he's got it!
> >
> Ain't gonna happen...
>
> The main purpose of a Cursor is to keep a pointer into the
> table as the rows
> are being processed.
>
> Since ER doesn't enforce the physical placement of the data,
> then a cursor
> on one server is meaningless on another.
>
> In fact Since ER is selective in what is replicated, we can't
> guarentee that
> the query plans on differing nodes will be the same....
>
> M.P.

Would it be doable in HDR?

Paul M.

<mosserp@wellsfargo.com> wrote in message
news:mailman.375.1138825942.740.informix-list@iiug.org...
Madison Pruet wrote:
> "Art S. Kagel" <kagel@bloomberg.net> wrote in message
> news:43E0E317.2080907@bloomberg.net...
> > bozon wrote:
> > > Art S. Kagel wrote:
> > >
> > >>bozon wrote:
> > >>
> > >>>It would help us. I think it would be a feature that
> would really fit
> > >>>in with the new redundant fault tolerant application
> structure that is
> > >>>popular today.
> > >>
> > >><SNIP>
> > >>
> > >>That raises an additional, related request. That the
> global cursor ID
> be
> > >>sharable across ER replicants. That would allow cost
> free failover to a
> > >>backup server!
> > >>
> >
> > By George I think he's got it!
> >
> Ain't gonna happen...
>
> The main purpose of a Cursor is to keep a pointer into the
> table as the rows
> are being processed.
>
> Since ER doesn't enforce the physical placement of the data,
> then a cursor
> on one server is meaningless on another.
>
> In fact Since ER is selective in what is replicated, we can't
> guarentee that
> the query plans on differing nodes will be the same....
>
> M.P.

Would it be doable in HDR?

Paul M.

more doable. There would be a major problem, however, because the the state
of the cursor changes with each and every row that you touch within the
query. That would mean a whole lot of network traffic.

M.P.