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.
Fred Prose — — source: Informix-list mailing list archive (1991-1998)
What is the prevailing thought about using BEGIN/COMMIT WORK within a Stored
Procedure?
I've got a SP which is called to obtain and increment a "next serial number"
column. This potentially will cause a bottle nexk and I'd like to have the
SP "get in and get out" ASAP.
Any other suggestions to make sure the SP isn't doing any dirty reads?
Thanks,
Your privacy choices
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.