Gladius allows names that consist of a single identifier or multiple identifiers. The components
of a multiple-part identifier must be separated by period (‘.’) characters. The initial parts of a
multiple-part identifier act as qualifiers that affect the context within which the final identifier is
interpreted.
Columns can be referenced using the following forms:
|
Column reference
|
Meaning
|
|
column_name
|
The column column_name from whichever table used in the
statement contains a column of that name.
|
|
table_name.column_name
|
The column column_name from table table_name of the
currently selected database.
|
If any components of a multiple-part name require quoting, quote them individually rather than
quoting the name as a whole. For example, write `my-table`.`my-column`, not `my-table.my-
column`.
Note: identifier quoting is not supported
You do not need to specify a table_name prefix for a column reference in a statement unless
the reference would be ambiguous. Suppose that tables table1 and table2 each contain a
column named c, and you retrieve c in a SELECT statement that uses both table1 and table2.
In this case, c is ambiguous because it is not unique among the tables used in the statement.
You must qualify it with a table name as table1.c or table2.c to indicate which table you mean.
A word that follows a period in a qualified name must be an identifier, so it is not necessary to
quote it, even if it is a reserved word.
Case sensitivity
Gladius databases correspond to directories within the Gladius database root directory. Each
table within a database corresponds to multiple files within the database directory.
Field names are case sensitive but cannot be case-insensitively equal to other field names of
the same table. This is due to OS filesystems limitations.
Database and table names are case insensitive and always converted to respectively lower
and upper case.