4 ms·

I've come to love jOOQ, the Java library that I can write type-safe pure SQL in (and with code that is immediately understandable to anyone who knows SQL). It p

I've come to love jOOQ, the Java library that I can write type-safe pure SQL in (and with code that is immediately understandable to anyone who knows SQL). It provides mechanisms to smooth the clash of Java/SQL worlds, but otherwise never assumes it is smarter than the wisdom accumulated through decades of database usage. I've come to appreciate many aspects of databases again that tools like Hibernate try to hide from me. http://www.jooq.org/ http://www.jooq.org/ I do still use Hibernate, probably because my usual framework of choice makes it so easy to, but anything above medium complexity goes through jOOQ nowadays.

_pmf_ 10y ago
I was intrigued by jOOQ, but the huge amount of generated code for internal metadata of the DB was a bit offputting. I don't want 4MB of generated classes for 3 very small tables.
- lukaseder 10y ago
  Use the code generator's <inputSchema> or <excludes> flag or other means and you'll only get those 3 small tables generated...
  - _pmf_ 10y ago
    Ah, thank you, this does the trick; I first tried to use my database name as inputSchema, but I had to use "public" in PG.
    - lukaseder 10y ago
      I see, yes. The database corresponds to jOOQ's Catalog, not the Schema (except in MySQL, which mixes up these concepts)