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

 

System procedure and function behavior changes

Following is a list of system procedure and function behavior changes added in SQL Anywhere version 16.0.

  • TRACEBACK function enhancements   The TRACEBACK function returns a call stack that is annotated with the object names and line numbers, which simplifies the process of locating the actual statements that are reported in the call stack. See TRACEBACK function [Miscellaneous].

  • Changes to SMTP and MAPI return codes   The following changes have been made to the return codes used by the xp_startmail, xp_startsmtp, xp_sendmail, xp_stopmail, and xp_stopsmtp system procedures:

    Return code Meaning in previous releases Meaning in version 16.0 databases Additional information
    -1 Unknown error New error code
    0 Success Success
    1 An invalid parameter was supplied New error code
    2 xp_startmail or xp_startsmtp failed Out of memory
    3 xp_stopmail or xp_stopsmtp failed xp_startmail or xp_startsmtp was not called
    4 Bad host name New error code
    5 xp_sendmail failed Connect error
    6 Secure connection error New error code
    7 MAPI functions are not available New error code

    The xp_get_mail_error_code and xp_get_mail_error_text system procedures return additional information about the return codes. You must upgrade existing databases to get the new system procedures and error codes. See:

    If your application cannot be changed to check for the updated return codes, you can configure the database server to use the return codes from previous releases of the software by using the version 12 dbext.dll file and the use_old_dbextf.sql script, located in the scripts subdirectory of your SQL Anywhere installation. See Database server deployment.

  • USER_NAME and SUSER_NAME functions now return VARCHAR   The user_name and suser_name functions now return data of type VARCHAR instead of LONG VARCHAR. If you have materialized views that use these functions, you need to rebuild them.

  • Error handling   To allow the LOAD TABLE operation when the statement encounters errors while inserting or parsing rows, problem rows can be written to a ROW LOG and an error message written to a MESSAGE LOG. After the specifiable number of errors is encountered, the statement fails and rolls back. The following clauses have been added to support this feature:

    • ALLOW...ERRORS
    • ROW LOG...
    • MESSAGE LOG...

    See LOAD TABLE statement.