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


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

InstantDB version 3.10 now available


InstantDB version 3.10 is now available from http://www.instantdb.co.uk.

Changes from version 3.00:
--------------------------

- Added the SQL extension to allow: 
  UPDATE tableName SET col = (SELECT...). 
- Added a SET DEFAULT_USERNAME uname [DEFAULT_PASSWORD pword] 
  statement. This sets the default username and password for 
  imports from other JDBC data sources. 
- IMPORTs from files now search the database properties directory 
  and allow files to use fully qualified path names. 
- Added SET INCREMENT_BASE {<base>|MAX} ON {<table>.<column> | ALL} 
  so that auto increment columns can use different base values. 
- db.TableEncrypt has been extended to allow for the encryption 
  of binary columns
- All calls to System.gc() made by InstantDB have now been removed. 
- Small negative currency values were printed out wrong. Fixed. 
- Relative URLs for specifying database properties files should 
  now work. 
- The outer join syntax did not allow for pseudo tablenames. Fixed. 
- Currency columns now accept values without the "." in them. 
  "$300" is interpreted as three hundred dollars. "300" is 
  iterpreted as three hundred cents (as before). 
- The interaction between outer joins and WHERE clauses was 
  incorrect. Row selection was done by filtering on the WHERE 
  and then adding and extending unmatched rows without further 
  regard to the WHERE clause. Extended rows must now match 
  the WHERE condition. 
- Now throws an exception when invalid escape characters are 
  detected in strings (e.g. "abc\kde"). 
- ResultSetMetaData.isAutoIncrement and isNullable have been 
  implemented correctly. 
- UNIQUE table constraints now constrain columns collectively 
  rather than individually. 



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