Changes for updating to v2.0.1

9 views
Skip to first unread message

Rob Bygrave

unread,
Jul 25, 2009, 5:44:30 AM7/25/09
to Ebean ORM

There are some changes you will potentially need to make to upgrade to
v2.0 that I forgot to note.


>> ebean.updatetimestamp.property=mVersion
>> ebean.updatetimestamp.dbcolumn=MVERSION
>> ebean.counter.property=vercount
>> ebean.counter.dbcolumn=vercount

These properties are no longer supported. You need to explicitly use a
@Version annotation now.



>> ebean.inserttimestamp.property=cretime
>> ebean.inserttimestamp.dbcolumn=cretime

These properties are no longer supported. You need to explicitly use a
@CreatedTimestamp annotation



>> ebean.namingconvention.property=com.example.MyNamingConvention

This was accidentally missed (a bug in v2.0.1). I'll log as a bug and
fix in the next version. As a workaround for the meantime you can use
ServerConfig explicitly.



>> ebean.identityGeneration=identity

In theory you only need this for DB2 or H2 which support both
sequences and identity/autoincrement. You need to explicitly use
ServerConfig and DatabasePlatform to set the identity.


Apologies,
Cheers, Rob.
Reply all
Reply to author
Forward
0 new messages