Druid, The Database Manager News

Hi all,

after 2 years a new release has born! As many of you already now, Druid now is not under active development so for this release we have to thank
Mark Heinze and Ruslan A. Bondar. I also had the chance to fix small things all around. Here is the list of new things:

Enhancements:
- JAVA JDO: Do not need to declare and import for classes in the same package
- JAVA JDO: Put in flag to convert '_' to CamelCase names in Java conversion
- Added possibility to specify the SQL terminator.
- Support for different sql dialects in SQL editor highlighting

Applied patches:
- [1832546] Oracle sequence order
- [1832535] Fix some unused imports
- [1719083] serial8 to int8 foreign key mapping patch for postgres

Changes:
- Now Druid is compiled with Java 1.5

Bugs fixed:
- [1709820] Spelling error
- [1449916] HSQLDB sequence generation error
- JDBC: Bypassed exception raised by MySQL when accessing table's privileges
- PostgreSQL module : Fixed generation of triggers
- PostgreSQL module : Fixed generation of foreign keys
- Fixed order of generating elements. Generation of functions was moved after tables. Cause - postgres may use virtual datatypes. Such as schema.table.field%TYPE

Please, notice 3 things:

- Mark's patch was backported from the main branch to the V3_X one. The Java JDO generator was already changed so I had a hard time in porting it. I hope it works, otherwise we have to do a fix release.

- Ruslan patch changed the order generation of sql objects. Before, it was: (sequences, functions, procedures, tables, views)
now it is: (sequences, tables, views, functions, procedures). Maybe, this can create problems with other DBMSs. In this case we will create a different sql generator.

- Sequences now have the INCREMENT BY clause after the START WITH one. This fixes the SQL for oracle and hsqldb but may break compatibility with other DBMSs.

These 3 things can create problems to users of other DBMSs. In this case, please let me know in order to fix the problem.

Cheers,
Andrea