Neoview Character Sets Administrator's Guide (R2.4, R2.5)

Table 3-1 Summary of SQL Language Rules by Neoview Character Set Configuration (continued)
Unicode ConfigurationSJIS ConfigurationISO88591 ConfigurationSQL Language Rule
SQL Identifiers
• SQL identifiers are stored
in UTF8 format, where
Unicode characters are
stored in one, two, three, or
four bytes. SQL identifiers
can be a maximum of 32 to
128 characters in length,
depending on the size of
the UTF8 characters stored.
For example, an SQL
identifier that uses a series
of 4-byte characters would
be limited to 32 characters.
• Delimited identifiers are
required.
• SQL identifiers can be a
maximum of 64 to 128
characters in length,
depending on the SJIS
characters stored.
• Delimited identifiers are
required.
• SQL identifiers can be up
to 128 characters (bytes)
in length.
• Regular identifiers are
used.
Size SQL identifiers as
dictated by the selected
configuration. SQL
identifiers are limited
to 128 byte lengths in
all three Neoview
character set
configurations, but the
number of characters
enclosed in the SQL
identifier can range
from 32 to 128.
Table names that are used by materialized views and triggers are limited to 110 bytes in all
three configurations. If you create a materialized view or trigger on a table, you must make
sure the table name does not exceed this limit. If it does, you must shorten the table name
to an acceptable size.
Comply with the
110-byte length limit
on table names that are
used by materialized
views and triggers.
If you are using a Neoview
ODBC driver, each client
workstation can only display
SQL identifiers and SQL data
encoded in the workstation's
currently-configured character
set. So use only 7-bit ASCII
characters in SQL identifiers
and SQL data if they will be
displayed on workstations
with different client locales.
For more information, see
Appendix B (page 47).
Not applicableNot applicableWhen necessary, use
7-bit ASCII encoding
for SQL identifiers and
SQL data to enforce
support for multiple
client locales.
Querying SQL Metadata
Because UCS2 is the default
column and metadata must be
stored in ISO88591 columns,
you must explicitly specify the
_ISO88591 prefix for every
literal value in the SQL
statement.
Not applicable because
ISO88591 is the default
column.
Not applicable because
ISO88591 is the default
column.
Applications that
access SQL metadata
must explicitly specify
prefix literals for
metadata.
Stored Procedures in Java
All literals for ISO88591
columns must be explicitly
defined with the prefix
_ISO88591.
All literals for UCS2 columns
must be explicitly defined
with the prefix _UCS2.
All literals for UCS2 columns
must be explicitly defined
with the prefix _UCS2.
If you use a character
string literal in a CALL
statement or as the
translated value for an
SQL statement inside a
stored procedure, you
must explicitly define
the prefix for every
character string in a
table column that is not
in the default character
set for the selected
Neoview character set
configuration.
Rules for Encoding SQL Language Elements 25