Thanks as always for the quick response! On Sat, Mar 24, 2012 at 1:18 PM, Lukas Eder <[email protected]> wrote: > > - Did you set <relations>true</relations> in your code-generator? >
Yes, this is the configuration in my pom.xml: https://gist.github.com/998fd6eb40fbed119ac6 Also, I'm using almost exactly the same type of structure elsewhere in my code with a different table and it works perfectly, so I think it might be something specific to this table. > Verify that the Campaign table overrides the Identity method to > provide jOOQ with the identity column (Campaign.ID). Here is my Campaigns table: https://gist.github.com/17bd372788848ee80d78 I don't see any mention of "identity", but it does have this: @Override public org.jooq.UniqueKey<amplify.jooq.tables.records.CampaignsRecord> getMainKey() { return amplify.jooq.Keys.KEY_CAMPAIGNS_PRIMARY; } > - What version of MySQL are you using? jOOQ officially supports 5.1 and > above > I'm using 5.5.20 > - What version of the MySQL JDBC driver are you using? I run > integration tests with mysql-connector-5.1.15 > 5.1.18 - should I try downgrading? In case it's useful, here is the mysql dump of the campaigns table: https://gist.github.com/46e5fa5f5a768725eb7c Thanks for your help! Ian. -- Ian Clarke Blog: http://blog.locut.us/
