Schema awareness is fine. Please just don’t handcuff the schema to a particular database instance, but allow it to be portable.
One thing that annoyed me with JOOQ vs QueryDSL in the Java world was that you could not point the same object you generated from a production server to a development server. You actually had to create an entirely new set of objects for the second box, even though the schema was identical.
Hi there, Lukas from the jOOQ team here. Just a short note to tell you that you might have been missing the runtime schema mapping feature in jOOQ:
http://www.jooq.org/doc/latest/manual/sql-building/dsl-context/runtime-schema-mapping
Using this, you can generate code from any server (e.g. production), and replace all schema / table names to match those from your development server, without re-generating all the objects. We’ve always had this feature in jOOQ, from the very beginning.
Hope this helps,
Lukas