Can we see this as a bugfix release or should we switch to 2.3.0? I suppose there are non-compatible api changes?
F On 11 March 2012 13:48, Rainer Döbele <[email protected]> wrote: > Hi folks, > > > > good news: Important issues have been resolved and I think now is a good time > for our first TLP release. > > > > Here's the Changelog: > > > > -------------- > > Release 2.2.1: > > -------------- > > ** New Feature > > * [EMPIREDB-79] - Allow specification of delete action for each > DBRelation (ON DELETE CASCADE) > > > > ** Improvement > > * [EMPIREDB-133] - Simplify use of DBCommand:DBCommandParam class > > * [EMPIREDB-129] - Allow expression based indexes > > * [EMPIREDB-126] - Various small improvements, like new method overloads, > code and javadoc cleanup, etc. > > * [EMPIREDB-123] - Allow to specify the character column length in bytes > (Non-Unicode) or chars (Unicode) for DDL generation > > > > ** Bugfix > > * [EMPIREDB-135] - Suppress column alias inside concatenations > > * [EMPIREDB-132] - Fix support for CLOB data type in Postgre SQL > > * [EMPIREDB-130] - Prepared Statements: Convert Enums to String to avoid > SQLException > > * [EMPIREDB-128] - Velocity Template Table.vm does not handle tables > without primary keys > > * [EMPIREDB-124] - Added missing Serializable on class commons.Options and > commons.OptionEntry > > * [EMPIREDB-122] - Fixed support for Update/ Insert of Chinese characters > with non-prepared statements > > * [EMPIREDB-121] - Fixed lower case expression for SQL-Server (lower > instead of lcase) > > * [EMPIREDB-120] - Fixed FieldIllegalValueException for DataType.DATETIME > and DataType.DATE if the value is empty (but DBTableColumn is nullable) > > > > Francis, can you go ahead starting the release process or is there anything I > should or must do? > > > > Regards > > Rainer > > >
