Home
SQL programmingYou can use the HCL OneDB™ implementation of the SQL language to develop applications for HCL OneDB™ database servers.
Guide to SQL: ReferenceThese topics contain the reference information for the system catalog tables, data types, and environment variables of the HCL OneDB™ dialect of the SQL language, as implemented in HCL OneDB™.The HCL OneDB™ Guide to SQL: Reference contains the reference information for the system catalog tables, data types, and environment variables of the HCL OneDB™ dialect of the SQL language, as implemented in HCL OneDB™. These topics also include information about the stores_demo, sales_demo, and superstore_demo databases that are included with HCL OneDB™.
Environment variablesVarious environment variables affect the functionality of your HCL OneDB™ products. You can set environment variables that identify your terminal, specify the location of your software and define other parameters.
Environment variables in HCL OneDB™ productsThe topics that follow discuss (in alphabetic order) environment variables that HCL OneDB™ database server products and their utilities use.
ANSIOWNER environment variableIn an ANSI-compliant database, you can prevent the default behavior of upshifting lowercase letters in owner names that are not delimited by quotation marks by setting the ANSIOWNER environment variable to 1.

ANSIOWNER environment variable

In an ANSI-compliant database, you can prevent the default behavior of upshifting lowercase letters in owner names that are not delimited by quotation marks by setting the ANSIOWNER environment variable to 1.

setenvANSIOWNER 1

To prevent upshifting of lowercase letters in owner names in an ANSI-compliant database, you must set ANSIOWNER before you initialize HCL OneDB™.

The following table shows how an ANSI-compliant database of HCL OneDB stores or reads the specified name of a database object called oblong if you were the owner of oblong and your userid (in all lowercase letters) were owen:

Table 1. Lettercase of implicit, unquoted, and quoted owner names, with and without ANSIOWNER
Owner Format	Specification	ANSIOWNER = 1	ANSIOWNER Not Set
Implicit:	oblong	owen.oblong	OWEN.oblong
Unquoted:	owen.oblong	owen.oblong	OWEN.oblong
Quoted:	'owen'.oblong	owen.oblong	owen.oblong

Because they do not match the lettercase of your userid, any SQL statements that specified the formats that are stored as OWEN.oblong would fail with errors.