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.
Declaring Keywords or Routine Names as SPL Variables

Declaring Keywords or Routine Names as SPL Variables

If you declare a variable with the same name as a keyword or as the name of a routine, ambiguities can occur. HCL OneDB™ uses the following rules for resolving name conflicts among SPL variables, UDR names, and built-in SQL function names.

Variable names that are declared in DEFINE statements take the highest precedence.
User-defined routines defined in CREATE PROCEDURE or CREATE FUNCTION statements take precedence over built-in SQL functions.
Procedures declared with the PROCEDURE keyword in the DEFINE statement take precedence over built-in SQL functions.
Built-in SQL functions take precedence over SPL procedures that exist in the database but that are not explicitly identified as procedures in the DEFINE statement.

Do not use the name of a built-in SQL function as an SPL variable if you might need to invoke the SQL function. For example, do not declare a variable with the name count or max, if you might also need to call those aggregate functions.