Cloudscape 3.0.4 Release Notes
March 20, 2000
Release Notes Top | Getting
Started
Upgrade Information
Before using Cloudscape 3.0.x with databases created with prior versions
of Cloudscape, read the documentation pertaining to upgrade issues. See
The Developer’s Guide.
NOTE: There is no guarantee of upgrade
path from 3.0 Beta databases to 3.0.x (GA) databases. There is an
upgrade path from 2.0.x databases to the 3.0.x GA release product.
For technical support, go to http://www.cloudscape.com/
and click Support.
What’s New in Version 3.0.4?
For information about bug fixes, see Information
About Previously Reported Limitations.
The following JDBC calls have
been implemented on the Statement Interface
-
getResultSetConcurrency()
-
setFetchSize(int rows)
-
getFetchDirection()
-
getFetchSize()
-
getMaxFieldSize()
-
setFetchSize()
-
setFetchDirection()
-
setEscapeProcessing()
-
setMaxRows()
-
getMaxRows()
-
getTime() with Timestamp
Escape syntax is now Supported
for Built-in Functions
The following DatabaseMetaData calls support Escape syntax:
-
getStringFunctions=BIT_LENGTH, CHAR_LENGTH, CHARACTER_LENGTH, LENGTH, LOWER,
LTRIM, OCTET_LENGTH, RTRIM, SUBSTR, SUBSTRING, TRIM, UPPER. (LENGTH is
only supported with escape syntax)
-
getSystemFunctions=CURRENT_USER, getCurrentConnection, runTimeStatistics,
SESSION_USER, USER
-
getTimeDateFunctions=CURDATE, CURTIME, CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
EXTRACT. (CURDATE and CURTIME are only supported with escape syntax)
-
getNumericFunctions= (no functions, this used to return something)
These methods now correctly return the built-in functions of that type
that are supported using the escape syntax.
What’s New in Version 3.0.1?
For information about bug fixes, see Information
About Previously Reported Limitations.
Non-standard Exceptions Changed
to SQLExceptions
Previously, some Cloudscape classes had methods that threw exceptions such
as StandardException, DatabaseException, and TypeException.
Beginning in 3.0.1, these methods now throw SQLExceptions instead,
for ease of use.
Location of NT Service Files Changed
Beginning in Version 3.0.1, the Cloudscape Windows installer puts NT Service
files (for starting the RmiJdbc server as an NT service) in a directory
called /services under the Cloudscape installation directory. In
prior releases, those files were in a folder in the RmiJdbc directory under
/frameworks.
What’s New in Version 3.0?
For information on the new features in Version 3.0, see Getting
Started with Cloudscape. This section lists only detailed changes
that might affect existing applications and scripts.
Changes to Installation Layout
-
/bin in the outermost directory has been deleted. Use the specific
/bin directory for your framework instead.
Changes to System Tables
-
New table, SYS.SYSTRIGGERS.
-
SYS.SYSALIASES replaces SYS.SYSMETHODALIASES and tracks all
alias types: method aliases, class aliases, user aggregates, and work units.
-
SYS.SYSCOLUMNS has a new column, COLUMNDEFAULTID. The use
of the COLUMNDEFAULT column is new.
-
SYS.SYSTABLES has a new column, LOCKGRANULARITY.
-
SYSERRORS table has new columns: PUBLICATIONID, STMTCOUNTERS,
and TRANCONTENTS.
New Properties
-
cloudscape.language.stalePlanCheckInterval
Note that the default value for this new property could change the
behavior of your application.
-
cloudscape.language.triggerMaximumRecursionLevel
-
cloudscape.locks.monitor
-
cloudscape.locks.waitTimeout
Note that the default value for this new property could change the
behavior of your application.
-
cloudscape.database.forceDatabaseLock
-
The behavior of the cloudscape.locks.deadlockTimeout property is
new.
-
The ability to set the cloudscape.storage.rowLocking property as
a database-wide property is new.
Changes to Demos
-
There are no longer VTI, applet and servlet demos downloadable from the
Cloudscape Web site. These demos have been incorporated into the JBMSTours
demo.
-
The pre-built version of the sample database, toursDB, in CLOUDSCAPE_INSTALL/demo/databases
now stores the jar file needed to access all Java data types in the demo.
JVM Support
Cloudscape JVM
For information about Cloudscape and JVMs, see The
Developer’s Guide.
Cloudview JVM
Cloudscape supports Cloudview in the following JVMs:
| Platform |
JDK |
| Windows NT |
JavaSoft 1.2 |
| Windows 98 |
JavaSoft 1.2.2 |
| Windows 95 |
JavaSoft 1.2 |
| Solaris 7 |
SunSoft JDK 1.2 |
|
| Linux |
1.1.7* |
| Novell |
Novell 1.1.7* |
| Macintosh |
Apple's MRJ 2.1 (Mac OS Runtime for Java, based on JavaSoft
JDK 1.1.6)* |
| RS6000 |
JDK 1.1.6* |
*You must download an additional library, swingall.jar,
from Cloudscape to work with this JDK. You can download this library from
http://www.cloudscape.com/support/Downloads.
ODBC Driver Compatibility
Cloudscape 3.0.x is compatible with Cloudscape ODBC driver version 2.0
build 191.
Known Limitations
Cloudview Limitations
Cloudview Disk Drive Search
Behavior
(Bug no. 0)
In Cloudview on Windows, while doing an open from the File menu, a message
from the operating system may get generated if there is a drive with the
disk removed (like a Zip or floppy drive without a disk inserted). The
message reads
There is no disk in the drive. Please insert a disk into drive.
If you press the Abort button, the drive with the missing disk will be
ignored. To avoid this message, either insert a disk into the drive, or
add a line to the SysVisual.properties file that describes a list of valid
drives. For example, if the list of valid drives on the system is a, c,
and x, then add a line that states
SysVisual.drives=acx
Note that no separator between the drive letters is necessary.
This behavior is caused by JDK1.1.x limitations.
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.
Menus Stop Working on Win98/JDK1.2
Along With Nonfatal JIT Error.
(Bug no. 2249)
On Windows 98 under a 1.2 JVM, some customers experience the following:
Menus in the menubar work normally for a few minutes and a few invocations,
then stop working; after that, clicking on a menu item highlights the word,
but the menu does not drop down. This behavior is accompanied by a nonfatal
internal JIT error.
NOTE: This is a Sun JVM bug (see bug numbers
4204218 and 4220211).
A possible workaround is to increase the max heap memory available to
java. Just use "-Xmx128m" or equivalent to set a very high max heap size.
Cloudview Is Behind On
Features
(Bug no. 2417)
Cloudview does not reflect all the features available in Cloudscape.
It currently does not support:
-
Schemas
-
Database properties
-
Class aliases
-
User-defined aggregates
-
Triggers
NOTE: Many items in Cloudview have an "SQL"
tab, which displays SQL statements you can use to re-create or drop the
displayed item. Note that the items listed in this section are likewise
missing from the displayed statements, so do not rely on these statements
to re-create your database.
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.
Batch and Shell Files and NT
Service Files Are Incorrect When Installing with Jview
(Bug no. 2211)
When you install Cloudscape using the Jview JVM, the Cloudscape installer
does not correctly modify batch and shell files and NT Service files and
so these files do not work correctly.
Can't Load Classes from Database
When Database Itself Is in Jar
(Bug no. 2458)
When you store a database as a read-only database in a jar file, you
can't load classes out of the database.
Documentation Errata and
Omissions
Stored Prepared Statements
The section "Stale Stored Prepared Statements" in the book Tuning Cloudscape
discusses that the statement plan for stored prepared statements can sometimes
go bad or "stale". This section states that you can recompile statements
explicitly, but it fails to mention that in many cases Cloudscape now automatically
recompiles such statements, so you probably do not have to recompile statements
by hand.
For a discussion of this new feature and how to configure it, see "Automatic
Stale Plan Invalidation" in the same book (doc/html/coredocs/depth1.htm#836292).
Information About Previously
Reported Limitations
Bugs Fixed Since the Previous
Release
| Bug no. |
Description |
Fixed in Version |
| 2022 |
RmiJdbc Client Classpath |
3.0.0 |
| 2582 |
Applications that Fail to Close ResultSets Can Sometimes
Get Deadlock in Finalizer |
3.0.1 |
| 2767 |
NullPointerException when Query Contains an OR Clause
on a View Containing a Join |
3.0.2 |
| 2769 |
NullPointerException when Query Contains a Table Alias
and Group and Order By Clauses |
3.0.2 |
| 2796 |
Metadata calls getImportedKeys and getExportedKeys take
too long |
3.0.2 |
| 2810 |
RunTimeStatistics now prints optimizer estimates at all
nodes |
3.0.2 |
| 2686 |
Cloudscape Installer Resets Path Incorrectly on Windows
98 |
3.0.3 |
| 2717 |
On Unix or Linux boxes, the Installation Defaults to
ROOT |
3.0.3 |
| 2744 |
Placing client.jar before cloudscape.jar in the classpath
produces Authentication error |
3.0.3 |
|
2780 |
XADataSource Throws XAException when TMJOINing an Idle
Local Connection to a Global Transaction |
3.0.3 |
Bugs Scheduled to be Fixed in
Cloudscape 3.5
| Bug no. |
Description |
Fixed in Version |
| 2788 |
statement.close() - statement can continue to be used
after close |
3.5.0 |
| 2789 |
statement.executeQuery(sql) - we allow non select query |
3.5.0 |
| 2789 |
statement.executeUpdate(sql) - we allow select query |
3.5.0 |