What's New in SQL Anywhere Studio
What's New in Version 6.0.1
This section describes behavior changes between version 6.0.0 and 6.0.1.
Java system table changes The system tables used to record Java class information (SYSJAR, SYSJARCOMPONENT, and SYSJAVACLASS ) had SMALLINT primary keys. These data types have been altered to use INTEGER primary keys. This change allows more Java classes to be stored in a database, and more changes to the Java classes in the database.
This change takes effect for new databases and databases upgraded using the Upgrade [dbupgrad] utility from this or future releases.
Parentheses in -x command line In previous releases, database server command lines using the -x option have used the brace character ({) to surround options. The same applies to the string in the CommLinks connection parameter. For example:
dbsrv9 -x tcpip{Localhost=demo}Existing command lines that use braces are still supported, but it is now recommended that you use parentheses to surround the options. Use of parentheses provides support for multi-byte character set identifiers in the database server command line and the CommLinks connection parameter.
dbsrv9 -x tcpip(Localhost=demo)
ANSINULL default for Transact-SQL and jConnect connections This has been changed to ON, which matches Adaptive Server Enterprise default behavior.
Database server -v option Prior to Version 6, this option produced verbose output to the transaction logs. This is obsolete, and -v is now used to supply version information.
Database server -gss option The behavior of the -gs server option, used to set the stack size, was complicated. The -gs option is now deprecated, and -gss provides the same functionality in a clearer way.
For more information, see The database server.
Character set conversion in Interactive SQL Formerly, when the CHAR_OEM_TRANSLATION option was set to DETECT, Interactive SQL would fetch the collation label from the database to determine whether or not OEM to ANSI character set translation would be turned on. If the collation label started with a string that indicated an ANSI code page, translation would be turned off. Otherwise it would be turned on. When the option was set to DETECT, Interactive SQL would display a message in the status window indicating the collation label of the database and the display translation setting.
The new behavior is as follows. If the option is set to DETECT, Interactive SQL will obtain the CharacterSet connection property from the server. This is the character set that the server is using for sending all character strings on this connection. If this character set indicates an ANSI code page, then OEM to ANSI translation is turned off. Otherwise it is turned on. A new message is displayed, indicating the collation label of the database, the character set used for communication over this connection, and the display translation setting.