demasi@paisana.UUCP (06/03/87)
Hello fellow informix users,
(Nothing here about commercialization of the group, so if you're
looking for an argument, hit the 'n' key)
Has anybody out there had the experience with informix (we're using
esql/c) that everytime you declare a cursor and query an active set,
and then do some non-readonly maneuver (ie an insert or update) it
for some reason destroys the cursor, and therefore active set you've
queried? Now I'm not just talking about a change that effects the
set you've queried, but even actions taken on totally different tables.
Am I doing something radically wrong? Have others had this problem?
When one uses the vanilla informix screens (we, unfortunately, are
using our own screen generation utilities) this problem does not seem
to arise. You can query up a whole load of records and then update,
insert or delete them until your little heart's content without ever
having to do another query. Is this just some wierd, internal logic
within the screen programs or am I missing something?
And by the way, has anybody yet figured out a way to do what I would
imagine one would have to call an 'unfetch' (That is, a way to back
the cursor up one row in an active set?) Again, I see no easy (or
at least not tremendously involved) way to do this from esql/c, but
again it's trivial from the vanilla informix screens.
Please reply with any answers (or comiserations) you may have,
--
Michael C. De Masi - AT&T Communications (For whom I work and not speak)
3702 Pender Drive, Fairfax, Virginia 22030 Phone: 703-246-9555
UUCP: seismo!decuac!grebyn!paisana!demasi
"No matter where you go, there you are" - Buckaroo Banzai