http://www.borland.com/jdatastore

Hit the yellow "Try it Now" button on the left.

------------------------------------------------------------------
Important:
------------------------------------------------------------------

This is a standalone version of JDataStore designed to be installed in its own folder.

Borland Enterprise Server 5.01 users already have this version of JDataStore included with their respective products.

------------------------------------------------------------------
To upgrade from a prior version follow the steps below
------------------------------------------------------------------

 install this version of JDataStore on its own directory;

 make a backup copy of the following jar's from either your \JBuilder\lib, or   
 \BorlandEnterpriseServer\lib subdirectory

 beandt.jar
 dbtools.jar
 jdsserver.jar
 jds.jar
 dx.jar
 jdsremote.jar

 replace with the ones from \JDataStore5\lib subdirectory

To verify which version of JDataStore you have, launch JDataStore Explorer or JDataStore Server and open the Help | About menu option.

For more information, check the release_notes.html file at the install directory.

------------------------------------------------------------------
Bug Fixes and Improvements
------------------------------------------------------------------

1) Incorrect values in result set of| select query with an order by clause from a table with an autoincrement column.

JDataStore crash recovery can corrupt database when system crashes while freeing up deleted files/tables or when deleting large blobs.

This defect has been fixed for 5.02.| Although most applications do not encounter this defect, the database can be corrupted when an application does encounter this defect.|

Here are the circumstances in which this defect can be encountered.| Note that all 3 conditions must be met for the defect to occur.

a) Your database has dropped tables with space that has not been released. When a JDataStore table is dropped, the space allocated to it is not immediately released.| The table is marked as deleted and JDataStore will release the space as new allocations are requested using a background FreeStreams thread.

b) The FreeStreams thread used to free up space allocated| to dropped tables is in the process of releasing blocks allocated to dropped tables

c) The JDataStore FreeStreams thread is not able to commit its transaction due to an application being stopped in the debugger, operating system crash or some other failure that does not allow the FreeStreams transaction to commit.| In this case the JDataStore crash recovery process can corrupt your database due to the fact that the FreeStreams transaction has logged an incorrect undo record.

It is recommended that JDataStore applications upgrade to 5.01 if possible to avoid this defect. For older installations of JDS, you can prevent the likelihood of encountering this defect by packing the JDataStore database after a table is dropped so that the FreeStreams thread will never need to be activated.

The JDataStore database verify can detect database corruption.| Verify can be activated through JdsExplorer or programmatically via com.borland.datastore.StreamVerifier.verify() method. Corrupted databases can be salvaged by using the JDataStoreExplorer Tools|Pack menu option or by using the com.borland.datastore.DataStoreConnection.copyStreams() method to copy the contents of the database into a new database.

By default, JDataStore 5.01 will create new databases with a new file format version of 9.| This keeps older versions of JDataStore classes from accessing newer JDataStore databases since the old versions of JDataStore classes have this defect.| Applications upgrade databases to file format version 9 by using the JDataStoreExplorer Tools|Pack menu option. Note that the JdsExplorer info tab displays the file format version next to the "Version:" label.

2) New JDataStore transaction log files cannot always be created under Win98.
When this occurs, applications typically encounter the following TxException error message: "com.borland.datastore.TxException: Cannot create new log files for JDataStore because a file with the name of C:\tmp\TestDebitCredit_LOGA_0000000000 already exists."

3) java.sql.DatabaseMetadata falsely returns an empty resultset when a table is created with the same column being the primary key and an autoincrement field.

Fixed.

4) Autoincrement value skips next value when database is shutdown and then restarted.

If values 0, 1, 2 where used for the autoincrement field for the first three rows added to a table, then when the database is shutdown and restarted, the next row added will now receive a value of 3 for its autoincrement field instead of 4.

5) The in-process local JDBC driver now restricts the number of open ResultSets per Statement to one.

This is behavior specified by the JDBC standard.| The TCP/IP based remote driver was already enforcing this behavior.

6) No pre allocation of blocks leading to a smaller size for .jds files

------------------------------------------------------------------

2002-Apr-19 6:58am gyles19@visi.com