Hi Rakesh,
Thanks for that feedback.
> Now Java+DB workflow becomes like this,
> 1) A framework for generating db structure from model classes { EBean,Play
> Model layer, Siena Project,Hibernate ? !! }
Yes, Hibernate supports three ways:
- Object => Mapping => DB
- Object <= Mapping => DB
- Object <= Mapping <= DB
> 2) A framework to automat db migrations {
> https://github.com/azomazo/migrate4j , It is on SF but the one GitHub
> supports Postgresql }
> well version controlled model layer from step 1 can act as a fresh db setup
> for specific version of the code.
I don't know if that's easy to accomplish. Some migration steps cannot
be "guessed" automatically, e.g. writing of E-Mail notifications about
changes, merging several fields into one, duplicating one field into
several fields, duplicating one record into several records, etc...
> 3) A framework for fluent queries [ this is what we do most of the time ] :
> JOOQ
I agree on that one :-)
> Now the way model layer provides hot reloading in development mode { Play !,
> and Siena does it } there has to be a hook from where we could generate JOOQ
> artifacts too upon change in model layer ! { ask play ! community if it's
> possible }.
What do you mean? You's like to change the database schema, and
immediately re-generate depending classes and hot deploy them? That's
probably not easy to achieve, when you add/remove static members, or
change the type hierarchy because you might add / remove keys. Maybe
with JRebel, if you can afford their licenses?
