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

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

Hi Everyone

Just to let you know, InstantDB 3.5 is now available from the usual place:

http://instantdb.enhydra.org/software/downloads/index.html

Many of you will be glad to know that, in addition to the changes listed
below, the download now contains a copy of the online documentation.

New Features

- New database property dateTimeFormat and new SQL statement:
SET DATETIME FORMAT <$ time>
- Date and time formats and currency symbols can now be defined on a per
column basis during table creation.
- DBBrowser and SQLBuilder have had all hard coded strings removed and
placed in ResourceBundles for easy future internationalisation.

Bug fixes

- Boolean parameters in PreparedStatements caused a ClassCastException
during expression evaluation. Fixed.
- ON DELETE... and ON UPDATE... could not be specified as table constraints.
Fixed.
- Multiple WHERE conditions could sometimes execute the wrong inequality
comparisons. Fixed.
- ALTER TABLE would fail and corrupt system tables if a column was added as
NOT NULL but with no DEFAULT value. Fixed.
- Multiple writing threads waiting for an existing writer, could wake up
when the write lock was freed, grab multiple read locks and then would
deadlock each other until the transaction timeout out. Read locks for
writers are now not grabbed until the write lock is also guaranteed.
- Timestamps used floating point arithmetic to set second and millisecond
values. This was subject to floating point rounding errors. Fixed.
- Scrollable results sets required a moveToInsertRow() call before every
insertRow() call. However, multiple calls to insertRow() should be allowed
after only a single call to moveToInsertRow(). Fixed.
- Updating of non-key fields in a parent table being referenced by a child
would be denied if the non-key field was not cached. Fixed.

Regards

Pete

--

Peter Hearty                         peter.hearty@lutris.com
Lutris Technologies (UK)        http://www.lutris.com


-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.