×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I think the implementation makes sense - it might have been a matter of
developer's or standards author's choice whether to set SQLSTATE (and
SQLCODE) to defaults (reset) before an SQL statement is processed or to
leave them at the value they had after the previous statement, then set
to defaults if there is no error. I've not read the SQL standards, so I
don't know what is said there. And I prefer what is happening now, as
one of these posts remarked is happening in the C++ code.
Nonetheless, we are told to save these return codes immediately after
any SQL statement has completed, so that we can use them to condition
further actions.
I used the term *SQL statement* above - I looked online and see that
many places refer to *IF statements*. So I'd need to see what the
standards call it.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
