We are happily using JOOQ with Java + Postgres. I strongly recommend it. Having statically typed representation of the schema has many pros and the trade-off i

We are happily using JOOQ with Java + Postgres. I strongly recommend it. Having statically typed representation of the schema has many pros and the trade-off is a little overhead when changing the db schema to regenerate classes. Some of the benefits include knowing exactly what part of the code stops compiling after changing the db schema, easily map POJOs to-from query results. Also, there's simply no pressure that you have to be absolutely certain what each and every knob on your ORM does else you have bad data in your database. Been burned before with Hibernate defaults, and the thought of a junior dev creating wrong conf is just not worth it. The database is basically the place were you least want a risk of misuse to have any unseen side effects.