Db first pojo second or reverse?

Question

Hi there,
I used to work with iBatis, first I used to design the database and then auto-generate the pojos/DAO from my db-design. Now I moved to hibernate.
Question: In hibernate, what approach is better to use, db first pojo second (create first the db and then reverse-engineer the pojo/daos) or pojo first - db second.
Thank you!

Answer 1

in a realistic environment the database is usually a given and cannot be (easily) changed by the developers.
More often than not the accounts you get simply won't have the authority needed to execute any DDL whatsoever.
In fact, in several environments I have worked in I didn't even have update access, the only database operations I was allowed to do were select statements and execution of a restricted set of stored procedures.
In such a situation, a Java first approach is obviously impossible.
Of course you could if you're starting from scratch install a local database and work in that, exporting the created table structure and giving it to a DBA in the hope he will recreate it inside the real database (but don't hold your breath, many of them won't do it, at best (for you) they'll change names, at worst (for you) they'll create something completely different that does the same thing more efficiently).
So you have to assume you will have to map an existing database to your application.