Home
Client APIs and toolsYou can use the HCL OneDB™ implementation of client APIs to develop applications for HCL OneDB™ database servers.
GLS User's GuideThese topics describe the Global Language Support (GLS) feature available in HCL® OneDB® products.The HCL OneDB™ GLS User's Guide describes the Global Language Support (GLS) feature available in HCL® OneDB® products.
SQL featuresThese topics explain how the GLS feature affects the HCL® OneDB® implementation of SQL.
Handle character dataThe GLS feature allows you to put non-ASCII characters (including multibyte characters) in the elements of an SQL statement.
Specify column substringsIn a query (or in any SQL statement containing an embedded SELECT statement), you can use bracket ( [ ] ) symbols to specify that only a subset of the data in a column of a character data type is to be retrieved. A column expression that includes brackets to signify a subset of the data in the column is known as a column substring.
Partial characters in an ORDER BY clausePartial characters might also create a problem when you specify column substrings in an ORDER BY clause of a SELECT statement.
Avoidance in TEXT and BYTE columnsPartial characters are not a problem when you specify a column substring for a column of the TEXT or BYTE data type.

Avoidance in TEXT and BYTE columns

Partial characters are not a problem when you specify a column substring for a column of the TEXT or BYTE data type.

The database server avoids partial characters in TEXT and BYTE columns in the following way:

Because the database server interprets a BYTE column as a series of bytes, not characters, the splitting of multibyte characters as a result of the byte range that a column substring specifies is not an issue.
A substring of a BYTE column returns the exact range of bytes that is specified and does not replace any bytes with white space characters.
The database server interprets a TEXT value as a character string.
A substring from a TEXT column returns the exact range of bytes that is specified. Attempts to resolve partial characters in TEXT data are resource-intensive, but the database server does not replace any bytes with white space. For more information, see The TEXT data type.

Important: The processing and interpretation of TEXT and BYTE data are the responsibility of the client application, which must handle the possibility of partial characters in these operations.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.