Yes, you're right. The current code-generator only generates DAOs for tables that have single-column primary keys, not composite primary keys. I had thought about this before, but I cannot find the relevant issue. Let's create one: https://github.com/jOOQ/jOOQ/issues/2573
Currently, org.jooq.Key does not refer to any Row type, which could be reused to group a row value expression into a composite key value (primary and / or foreign key). This could be changed in jOOQ 4.0 to better support row types of composite primary and / or foreign keys: https://github.com/jOOQ/jOOQ/issues/2574 I'm sure that other features related to #2574 could be derived from these thoughts Cheers Lukas 2013/6/29 Venkat Sadasivam <[email protected]> > It would be handy if DAO classes created for composite primary key tables > as well. > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
