Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » SQL Anywhere 16 - Changes and Upgrading » What's new in version 16.0 » SQL Anywhere behavior changes

 

Programming interface behavior changes

Following is a list of behavior changes to programming interfaces introduced in SQL Anywhere version 16.0.

  • Out of memory fatal error   On Windows, previous versions of the client libraries could attempt to display an Out of memory window when a client library routine was not able to acquire dynamic memory. It would wait for a user response and then terminate the application. The client libraries no longer do this. Now when an out of memory condition arises, a Windows event log entry is written under event source SQLANY16.0 (32-bit applications) or SQLANY64 16.0 (64-bit applications). After writing the event log entry, the software continues to execute permitting the requesting routine to handle this error condition. This change prevents client applications that are written as Windows services from hanging. It is up to the client application developer to determine the cause of an application exhausting all available memory. See Formatting Event Log messages.

  • ODBC SQLTables function   The SQLTables function has been corrected to categorize the dbo-owned system tables installed by the CREATE DATABASE statement as SYSTEM TABLE rather than TABLE (in the TABLE_TYPE column of the result set). Tables such as dbo.jdbc_function_escapes and dbo.spt_jdatatype_info are now classified as system tables.

    The SQLTables function has been corrected to categorize the dbo-owned system views installed by the CREATE DATABASE statement as SYSTEM VIEW rather than VIEW (in the TABLE_TYPE column of the result set). Views such as dbo.systypes and dbo.sysusers are now classified as system views.

  • JDBC DatabaseMetaData.getTables method   The getTables method of the DatabaseMetaData class has been corrected to categorize the dbo-owned system tables installed by the CREATE DATABASE statement as SYSTEM TABLE rather than TABLE (in the TABLE_TYPE column of the result set). Tables such as dbo.jdbc_function_escapes and dbo.spt_jdatatype_info are now classified as system tables.

    The getTables method has been corrected to categorize the dbo-owned system views installed by the CREATE DATABASE statement as SYSTEM VIEW rather than VIEW (in the TABLE_TYPE column of the result set). Views such as dbo.systypes and dbo.sysusers are now classified as system views.

  • Database Tools C API changes   The script_full_path field has been removed from the a_sync_db structure. Use of this field has not been supported since version 8.x. See a_sync_db structure [database tools].

    New fields (wait_before_start, wait_after_end, backup_comment, auto_tune_writers, and backup_history) and enumerations have been added to the a_backup_db structure. See a_backup_db structure [database tools].

  • Identifier rules and datatype limitations now enforced for JSON objects   JSON object identifiers must comply with the identifier rules defined in the database server. As well, the database server enforces the same limits for JSON data types as it does for the underlying ROW and ARRAY data types.