Browse Prior Art Database

SQL Ignore Error Feature Disclosure Number: IPCOM000016793D
Original Publication Date: 2003-Jul-15
Included in the Prior Art Database: 2003-Jul-15
Document File: 2 page(s) / 40K

Publishing Venue



SQL script scripts often produce many errors which may be safely ignored by the enduser. However numerous ignorable errors may hide real errors that need to be dealt with. This paper describes a new SQL statement that could suppress select ignorable error messages so that only real errors will shown to the enduser.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 63% of the total text.

Page 1 of 2

SQL Ignore Error Feature

When writing DBMS programs, SQL scripts are often employed to create and delete tables, to alter attributes on existing tables, or to populate newly created tables with values. For some systems these scripts can be very large and will issue many errors that are ignored by the developer. However when these scripts are shipped to customer sites for deployment, customers may view the output and become concerned with the errors, warnings and other messages generated by the DBMS SQL script processor, sometimes even contacting DBMS Product Support, where they are told that these errors and warnings are expected and should be ignored.

This paper addresses this concern by proposing that the DBMS SQL Script processor provide a new SQL statement that allows the developer to state what errors can be ignored and not displayed when the script is run. The new SQL statement might have the following syntax and which works along the following lines:

IGNORE {ALL | NEXT {#} } {list of message labels}

Error messages SQL21034E and SQL0204N often pop up when you attempt to drop a table that isn't there. Developers often make scripts that drop tables prior to creating them allowing some economy of script reuse when the database is present. However the first time these scripts are used the "SQL21034E -- DROPPING non-existent table" errors occur along with "SQL0204N -- Identifier not found" errors.

A sample script illustrates the use of this SQL statement:

-- Thi...