Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Atul Patankar — — source: Informix-list mailing list archive (1991-1998)
jparker@hpbs2561.boi.hp.com<19 Apr 1993 20:33:06 -0400> wrote
>Use the cursor to retrieve rowid and nothing else. When the user does a
>next/prev/whatever, use the rowid returned from the fetch xxxx to actually
>retrieve the row. Guarantees fresh data. Of course you still have to worry
>about someone deleting a row (which you did before anyway).
While using rowids with Online in one of the applications, I remember finding
that rowids that get freed due to a deleted row can get used again for a new
row. That new row may not be the one you need to see. I stopped relying on
rowids after that. Selecting a primary key is a much safer way to go. You can
avoid crashing for deleted rows if you keep track of the status variable.
Does SE behave any differently for rowids?
regards-
Atul.
--------------------------------------------------------------------------------Atul Patankar
email: apatanka@magnus.acs.ohio-state.edu Phone: (614) 575 6652
#include <std.disclaimer>
--------------------------------------------------------------------------------
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.