Hi Sander, I have just thought of another application of your idea of having interfaces instead of classes for Table/Record types: In many RDBMS, stored functions can return cursors/resultsets/tables (I'm currently implementing support for that for jOOQ 1.6.2). Some RDBMS even expose the concrete type for those cursors. With interfaces, it might be easier to hide a stored function behind an org.jooq.Table and to select from it.
Actually, Postgres has some of the most peculiar implementations for this. When you select from a function that has OUT parameters, every OUT parameter will result in a table column... that's quite interesting Cheers Lukas
