Mark A wrote:
Robert wrote:
>Am I right in thinking that different suppliers use consistently
different SQLCODEs for the same errors and that intellectual property
rights laws probably ensured that they had to do so. However, I
believe that they all use +100 for no data. SQLSTATE provides more
detail and also provides some logical grouping of error categories.
Robert
There are no intellectual property issues. The SQLSTATE was
specifically added to the SQLCODE to allow everyone to use a standard
set of error messages. However, like many other standards, not all
vendors have adhered to them.
It probably can be used with some sucess to port applications accross
various IBM relational products.
Across the DB2 family both SQLCODE and SQLSTATE are quite portable.
(Quite as in there are exception, but we maintain a central and shared
catalog of our error codes).
Teh story on SQLCODEs is that in the early days of System R, some
upstart company called Oracle asked for System R's SQLCODEs.
IBM, at that time not particularly standards oriented and quite possibly
a tad ;-) arrogant declined. Now we got the mess...
Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/