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.
Mark Palumbo — — source: Informix-list mailing list archive (1991-1998)
Do you think it is "ok" for us to continue our ESQL/C development
using the SQLCODE to check for Informix errors as opposed to the
new GET DIAGNOSTICS and SQLSTATE method?
Will SQLCODE support go away in future versions of Informix?
The Informix-ESQL/C "Programmer's Manual Version 7.2" recommends
the use of the new method, however, gives little support as to why.
X/Open and ANSI compiliance are not important to us (gasp) and we
typically do not care if multiple errors occur. (The stated
benefits of the new error checking method)
Your thoughts and opinions would be appreciated. Thank you.
------------------------------------------------------------------------
Mark Palumbo
Roadway Express, Inc.
Field Systems Development
Akron, Ohio USA
--
------------------------------------------------------------------------
Mark Palumbo, hc33 @ x3332 Field Systems Development
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.