Home
SQL programmingYou can use the HCL OneDB™ implementation of the SQL language to develop applications for HCL OneDB™ database servers.
Guide to SQL: SyntaxThe HCL OneDB™ Guide to SQL: Syntax describes the syntax of the statements, data types, expressions, operators, and built-in functions of the HCL OneDB™ dialect of the SQL language.
Other syntax segmentsThese topics describe syntax segments, which are language elements, such as database object names or optimizer directives, that appear as a subdiagram reference in the syntax diagrams of some SQL or SPL statements.
IdentifierAn identifier specifies the unqualified name of a database object, such as an access method, aggregate, alias, blobspace, cast, column, constraint, correlation, data type, index, operator class, partition, procedure, table, trigger, sequence, synonym, or view. Use the Identifier segment whenever you see a reference to an identifier in a syntax diagram.
Using keywords as table namesThe database server issues an error in contexts where the unqualified identifier of a table object is also a valid keyword of SQL. You can disambiguate the table name by qualifying it with the authorization identifier of the owner of the table.
SET keyword in the ON EXCEPTION statement of SPLIf you include an SQL statement that begins with the keyword SET in the ON EXCEPTION statement, you must enclose it in a BEGIN ... END statement block.

SET keyword in the ON EXCEPTION statement of SPL

If you include an SQL statement that begins with the keyword SET in the ON EXCEPTION statement, you must enclose it in a BEGIN ... END statement block.

The following list shows some of the SQL statements that begin with the keyword SET:

SET AUTOFREE
SET CONNECTION
SET CONSTRAINTS
SET DATASKIP
SET DEBUG FILE
SET DEFERRED_PREPARE
SET DESCRIPTOR
SET ENCRYPTION
SET ENVIRONMENT
SET EXPLAIN
SET INDEXES
SET ISOLATION
SET LOCK MODE
SET LOG
SET OPTIMIZATION
SET PDQPRIORITY
SET PLOAD FILE
SET ROLE
SET STATEMENT CACHE
SET TABLE
SET TRANSACTION
SET TRIGGERS

The following examples show the incorrect and correct use of a SET LOCK MODE statement inside an ON EXCEPTION statement.

The following ON EXCEPTION statement returns an error because the SET LOCK MODE statement is not enclosed in a BEGIN ... END statement block:

ON EXCEPTION IN (-107)
   SET LOCK MODE TO WAIT; -- error, value expected, not 'lock'
END EXCEPTION;

The following ON EXCEPTION statement executes successfully because the SET LOCK MODE statement is enclosed in a BEGIN ... END statement block:

ON EXCEPTION IN (-107)
   BEGIN
   SET LOCK MODE TO WAIT; -- ok
   END
END EXCEPTION;