Naming

Name Resolution

Most database objects (tables, views, etc.) can be addressed using a qualified name, by prefixing the name of the object with the name of its containing schema, separated by a dot; e.g.:

1

<schema name>.<table/view name>

For the full list of schema-contained objects, see CREATE SCHEMA.

If these objects are referenced without a schema, they will be looked for in the user's default schema, if one has been assigned.

The default schema can be overridden within an ODBC/JDBC session by issuing the SET CURRENT SCHEMA command. Once set, the new schema will be used to resolve unqualified names instead of the default schema--the user's default schema will be ignored for the purposes of name resolution.

Naming Criteria

Each database object is identified by a name, which will have the following SQL validation applied:

• Between 1 and 200 characters long
• First character is alphabetic, _, or #; if the object name is double-quoted, it can start with a number
• Each subsequent character must be alphanumeric, _, or #; if the object name is double-quoted, the following symbols, including spaces, can be used: { } [ ] ( ) : -
• Unique within its containing schema--cannot have the same name as another object of the same type in the same schema (two credentials can't have the same name in the same schema); tables & views are of the same "type" for this rule (a table can't have the same name as a view in the same schema)

Column names must meet the following criteria:

• Between 1 and 200 characters long
• First character is alphabetic or _; if the object name is double-quoted, it can start with a number
• Alphanumeric, including this symbol: _; if the object name is double-quoted, the following symbols can be used: { } [ ] : .

1
   2
   3
   

SELECT "1st.name", "last.name"
   FROM "employee-sync"."1on1s"
   ORDER BY "1st.name"
   

Reserved Words

For a list of the reserved words within Kinetica see SQL Reserved Word List.