Cloudscape automatically upgrades databases from versions prior to 3.6 to Cloudscape Version 3.6 databases. However, there is no automatic upgrade path from Cloudscape Version 3.6 Beta databases to Version 3.6 (GA) databases.
For complete instructions on how to upgrade a database, see the Cloudscape Developer's Guide.
Cloudscape is 100% pure Java and will run on any certified JVM. For a list of JVMs that have been tested with Cloudscape Version 3.6, look for information on http://www.cloudscape.com/support/TechInfo. You will also find some platform-specific information that may make it easier to get started with Cloudscape on some unusual platforms.
Cloudscape Version 3.6 is compatible with Cloudscape ODBC driver version 2.0 build 194.
Cloudview does not provide an interface for creating schemas.
Cloudview running in jdk1.1.7 and jdk1.1.8 gets hashtable overflows after a short period, on all platforms. This is a JVM bug and has been resolved in JDK 1.2.
Cloudview window shows only a limited number of characters for the separator character for delimited import or export. However, you can choose your own separator character by blanking out the field and adding your own separator character, for example, "|".
Dates that are before the year 1000 and greater than 199 will sort later than years in the range 1000-1999.
setAsciiStream() does not work on LONG VARBINARY columns; use setBinaryStream instead.
German and Spanish extended characters may display as garbage characters when the Cloudscape tools (sysinfo, ij) are run from a command prompt. To fix, change the MS-DOS prompt font to Lucida Console, and then run the following MS-DOS command before invoking the tools:
mode con codepage select=1252
For performance reasons, Cloudscape should transform queries like this one:
SELECT * FROM mytable WHERE mynvarcharcolumn LIKE 'constant'
Cloudscape should transform the LIKE operator to = so that the query executes faster. Currently Cloudscape makes this transformation in cases in which the column is a regular text column but not in cases in which the column is a national string column (NCHAR, NVARCHAR, and the like).
The ODBC documentation erroneously states that the version 2.0 Cloudscape ODBC Driver is compatible only with Cloudscape Version 2.0. It should say that the version 2.0 ODBC Driver is compatible with all versions of Cloudscape 2.0 or higher.
Cloudscape allows you to specify the encryption provider and algorithm when you create an encrypted database. Do not attempt to boot the database with a different provider; you must continue to use the provider with which you originally encrypted the database.
This is the expected behavior, but this warning may not be explicit enough in the documentation.
Cloudview online help and the Cloudscape Tools and Utilities Guide note that you can now use import/export with columns that have autoincrement defaults; the Cloudscape Tools and Utilities Guide states: "You can preserve the values in the autoincrement default column by dropping the default before importing the data and then re-adding the default when you are done importing."
Here are some more explicit instructions on how to do this.
ALTER TABLE mytable MODIFY myautoincrementcolumn DEFAULT NULL
ALTER TABLE mytable MODIFY myautoincrementcolumn DEFAULT AUTOINCREMENT
Cloudscape Version 3.6
For information about Cloudscape technical support, go to: www.cloudscape.com/support/.