This chapter provides an overview of the features of Caché SQL, especially those that are not covered by the SQL standard or are related to the Caché Unified Data Architecture. It assumes prior knowledge of SQL and is not designed to serve as an introduction to SQL concepts or syntax.
This chapter discusses the following topics:
Within Caché SQL, data is presented within tables
. Each table is defined to contain a number of columns
. A table may contain zero or more rows of data values. The following terms are roughly equivalent:
||Relational Database Terms
There are two basic types of tables: base tables
(which contain data and are usually referred to simply as tables) and views
(which present a logical view based on one or more tables).
SQL schemas provides a means of grouping sets of related tables, views, stored procedures, and cached queries. The use of schemas helps prevent naming collisions at the table level, because a table, view, or stored procedure name must only be unique within its schema. An application can specify tables in multiple schemas.
SQL schemas correspond to persistent class packages. Commonly a schema has the same name as its corresponding package, but these names may differ because of different schema naming conventions
or because different names have been deliberately specified. Schema-to-package mapping is further described in SQL to Class Name Transformations
Schemas are defined within a specific namespace. A schema name must be unique within its namespace. A schema (and its corresponding package) is automatically created when the first item is assigned to it and automatically deleted when the last item is deleted from it.
You can specify an SQL name as qualified or unqualified. A qualified name specifies the schema: schema.name
. An unqualified name does not specify the schema: name
. If you do not specify the schema, Caché supplies the schema as follows:
To view all the existing schemas within a namespace:
From the Management Portal
select System Explorer
, then SQL
. Select a namespace with the Switch
option at the top of the page; this displays the list of available namespaces. Select a namespace.
Select the Schema
drop-down list on the left side of the screen. This displays a list of the schemas in the current namespace. Select a schema from this list; the selected name appears in the Schema
The applies to
drop-down list allows you to select Tables, Views, Procedures, or Cached Queries, or All of these that belong to the schema. After setting this option, click the triangles to view a list of the items. If there are no items, clicking a triangle has no effect.
Within Caché SQL, you view and modify data within tables by means of queries
. Roughly speaking, queries come in two flavors: those that retrieve data (SELECT
statements), and those that modify data (INSERT
, and DELETE
You can use SQL queries in a number of ways:
Caché SQL uses a SelectMode option
to specify how data is to be displayed or stored. The available options are Logical, Display, and ODBC. Data is stored internally in Logical mode, and can be displayed in any of these modes. Every data type class can define transformations between internal Logical format and Display format or ODBC format by using the LogicalToDisplay()
, and ODBCToLogical()
methods. When SQL SelectMode is Display, the LogicalToDisplay transformation is applied, and returned values are formatted for display. The default SQL SelectMode is Logical; thus by default returned values are displayed in their storage format.
SelectMode affects the format that in which query result set data is displayed, SelectMode also affects the format in which data values should be supplied, for example in the WHERE clause. Caché applies the appropriate transformation method based on the storage mode and the specified SelectMode. A mismatch between a supplied data value and the SelectMode can result in an error or in erroneous results. For example, if DOB is a date stored in $HOROLOG Logical format, and a WHERE clause specifies WHERE DOB > 20000101
(ODBC format), SelectMode = ODBC returns the intended results. SelectMode = Display generates SQLCODE -146 Unable to convert date input to a valid logical date value
. SelectMode = Logical attempts to parse 20000101
as a Logical date value, and returns zero rows.
For most data types, the three SelectMode modes return the same results. The following data types are affected by the SelectMode option:
The SQL SelectMode may be specified as follows:
For Embedded SQL, using the ObjectScript #SQLCompile Select
preprocessor directive setting. This directive allows for a fourth value, Runtime, which sets the select mode to whatever the RuntimeMode
property setting is: Logical, Display, or ODBC. The RuntimeMode
default is Logical.
Collation specifies how values are ordered and compared, and is part of both Caché SQL and Caché objects.
You can specify a collation type as part of field/property definition. Unless otherwise specified, a string field/property defaults to the namespace default collation. By default, the namespace default collation for strings is SQLUPPER. SQLUPPER collation transforms strings into uppercase for the purposes of sorting and comparing. Thus, unless otherwise specified, string ordering and comparison is not case-sensitive.
You can specify a collation type as part of index definition, or use the collation type of the indexed field.
An SQL query can override the defined field/property collation type by applying a collation function to a field name. The ORDER BY
clause specifies the result set sequence for a query; if a specified string field is defined as SQLUPPER, query results order is not case-sensitive.
Caché supports numerous ways to write and execute SQL code. These include:
You can use Caché objects (classes and methods) to: