Re: Another IDS Feature Request

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. > > All that I'd want would be the ability to suspend an active session, disconnect, reconnect and then awaken the suspended session - exec it, iow. So that the session, if you like, goes from cond_wait(netnorm) to cond_wait(http_norm) and back again. -- rh