You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@empire-db.apache.org by Rainer Döbele <do...@esteam.de> on 2012/03/11 13:48:23 UTC
Release time!
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
re: Release time!
Posted by Rainer Döbele <do...@esteam.de>.
Hi Francis,
in fact yes, it's more than just a bugfix release.
Although there are no real API changes (as far as I remember) but some important enhancements, I think this would justify a 2.3.
I was having the same thoughts ealier on.
I leave it up to you to give it a number - I am fine with whatever you choose.
Regards
Rainer
> from: Francis De Brabandere [mailto:francisdb@gmail.com]
> to: dev@empire-db.apache.org
> re: Re: Release time!
>
> 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 <do...@esteam.de> 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
> >
> >
> >
Re: Release time!
Posted by Francis De Brabandere <fr...@gmail.com>.
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 <do...@esteam.de> 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
>
>
>