Cloudscape 3.6 Release Notes

November 20, 2000

Upgrade Information

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.

What's New in Version 3.6?

New Features




Changes to Cloudscape That Might Affect Existing Applications

Cloudscape and Platforms

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 You will also find some platform-specific information that may make it easier to get started with Cloudscape on some unusual platforms.

ODBC Driver Compatibility

Cloudscape Version 3.6 is compatible with Cloudscape ODBC driver version 2.0 build 194.

Known Limitations and Bug Fixes

Cloudview Limitations

Cloudview Is Behind On Features

Bug no. 3427

Cloudview does not provide an interface for creating schemas.

Hashtable Overflows on Cloudview on JDK 1.1.7 and 1.1.8 on All Platforms

Bug no. 1572

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 Limited Number of Characters for Import/Export Separator Character

Bug no. 3548

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, "|".

Database Limitations

Incorrect Date Sorting

Bug no. 1683

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

Bug no. 2878

setAsciiStream() does not work on LONG VARBINARY columns; use setBinaryStream instead.

On Windows Systems, German and Spanish Extended Characters May Display As Garbage Characters in Command Prompt Windows

Bug no. (Bug no. 3093)

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 

Cloudscape Should Transform Queries That Use LIKE Keyword to Compare to a Constant

Bug no. 3578

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).

Bugs Fixed in Cloudscape Version 3.6

Bug No.


Fixed in Version


Preparing a statement in autocommit mode should release locks on system tables when prepare is done.



Cloudscape error messages should specify the name of a constraint if a constraint is violated.



A newly created table causes lock on a system table if no rows are inserted before attempting to select from the table.



Streaming column should not materialize entire column in memory.



When a deferred insert occurs caused by a trigger and autocommit is false, a duplicate row could be inserted.


Documentation Errata

ODBC Documentation Lists Wrong Version Number

Bug no. 3204

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.

Do Not Change Encryption Provider After Creating an Encrypted Database

Bug no. 3511

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.

More Instructions on How to Use Import/Export with Autoincrement Defaults

Bug no. 3547

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.

  1. Export the data the way you normally would.
  2. Drop the autoincrement default.You can do this from Cloudview by deselecting "Auto Increment" for the column on the table tab. From SQL, you can do this with a statement like this:

    ALTER TABLE mytable MODIFY myautoincrementcolumn DEFAULT NULL

  3. Re-import the data the way you normally would.
  4. Re-add the autoincrement default. You can do this from Cloudview by selecting "Auto Increment" for the column on the table tab. From SQL, you can do this with a statement like this:

    ALTER TABLE mytable MODIFY myautoincrementcolumn DEFAULT AUTOINCREMENT