UltraLite behavior changes and deprecated features

Following is a list of deprecated features and behavior changes to UltraLite introduced in version 16.0. For information about supported platforms and versions, see [external link] http://www.sybase.com/detail?id=1061806.

Note

As with all forward-looking statements, the lists of deprecated features are not guaranteed to be complete and are subject to change.

Behavior changes

ECC support has been removed UltraLite C/C++ and UltraLiteJ API methods and properties related to ECC configuration have been removed. See Elliptic curve encryption (ECC).
Visual Studio 2005 project files for the CustDB sample have been removed The Visual Studio 2005 project files for the CustDB sample have been removed from the software.
The Visual Studio 2008 project files are now located in the %SQLANYSAMP16%\UltraLite\CustDB directory.

You can upgrade the Visual Studio 2008 project files of the CustDB sample by opening them in Visual Studio 2010.
Encryption control for BlackBerry smartphones is now built-in The ConfigPersistent.setEncryption method has been removed. Encryption control, where custom encryption code had to be supplied to the UltraLiteJ API to encrypt an UltraLite Java edition database, is no longer supported.
UltraLite Java edition databases are automatically checkpointed when statements are committed The following members have been removed from the UltraLiteJ API:
- ConfigPersistent.getAutoCheckpoint
- ConfigPersistent.setAutoCheckpoint
- Connection.checkpoint
Support for non-persistent indexes and non-shadow paging stores has been removed for BlackBerry smartphones UltraLite Java edition databases can no longer be created with non-persistent indexes or shadow paging turned off.
The following members have been removed from the UltraLiteJ API:
- ConfigPersistent.hasPersistentIndexes
- ConfigPersistent.setIndexPersistence
- ConfigPersistent.setShadowPaging
Support for write-at-end persistent stores has been removed for BlackBerry smartphones UltraLite Java edition databases can no longer be created as write-at-end databases.
The following members have been removed from the UltraLiteJ API:
- ConfigPersistent.setWriteAtEnd
- ConfigPersistent.writeAtEnd
UltraLiteJ getEncryptionKey and setEncryptionKey methods are synonymous with getDatabaseKey and setDatabaseKey methods, respectively New ConfigPersistent.getEncryptionKey and ConfigPersistent.setEncryptionKey methods have been added to the UltraLiteJ API.
See:
- ConfigPersistent.getEncryptionKey method [UltraLiteJ]
- ConfigPersistent.setEncryptionKey method [UltraLiteJ]
UltraLite Java edition utilities have been renamed UltraLite Java edition utility names now only contain lowercase characters so that they are consistent with the UltraLite utility names. See UltraLite Java edition utilities.
Column names are now always sent during synchronization You can no longer control the sending of column names. See Send column names.

Removed platforms

Removed APIs

UltraLite for M-Business Anywhere has been removed The UltraLite for M-Business Anywhere API is no longer supported.
Previous implementation of UltraLite C/C++ has been removed The old UltraLite C/C++ API implementation, previously defined in the ulcpp11.cpp and uliface.h files, is no longer supported.

Discuter à propos de cette page dans DocCommentXchange.