InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples

CVS Repositories

Who We Are
News, Articles & Events
Getting Involved
Contact Us

Case Studies
On The Edge! -NEW-
Commercial Vendors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ANN: InstantDB V3.15 beta 5

Beta 5 of V3.13 is now available from Apart from
the addition of a new function (position) and movement of partitioned table
indexes onto the partitions themselves, this is mostly a bug fix release:

- \\ handling in LIKE clause didn't work. Fixed.
- GROUP BY didn't work in second run of a PreparedStatement. Fixed.
- SMALLCHAR data type didn't handle NULL processing correctly. Fixed.

The full change history since 3.12 is as follows.

- Now accepts SELECT tableName.* from table...
- Alternative locations for new tables can now be specified. Indexes are
created in same place as alternate location tables.
- Statement.setQueryTimeout() has now been fully implemented.
- PreparedStatement.setXXXXstream() functions now implemented.
- New property "timerCheck" added.
- Non-updateable ResultSets now do a commit in auto-commit mode as soon as
the results have been fetched. i.e. Table locks are freed even if the whole
results set has not been read.
- Minor enhancement to JDBCAppl to allow <ENTER> after URL or SQL entry.
- LIKE clauses did not handle \\ correctly. Fixed.
- GROUP BY did not execute correctly on second run of a prepared statement.
- SMALLCHAR did not process NULLs correctly. Fixed.
- Statement.setMaxRows(int) would truncate results sets prematurely even if
an ORDER BY was included. This made it impossible to fetch the "top" or
"bottom" set of values from a table. Fixed.
- The read ahead cache was not updated when rows got deleted from large
tables. Fixed.
- UNIQUE PRIMARY KEYs would sometimes allow duplicates. Fixed.
- Adding a binary column using ALTER TABLE caused an exception. Fixed.
- Bug when updating binary encrypted fields. Fixed.
- Index builds which utilise a large number of similar keys were very slow.
- Table names appearing in the SELECT part of GROUP BY expressions sometimes
caused parsing errors. Fixed.


Peter Hearty
Instant Computer Solutions

To unsubscribe from this list, please send an
email to '' with the text
'unsubscribe instantdb' in the message body.