Lukas, I've been playing with 3.2.2 in my sandbox and ran into an issue in my app. While trying to recreate in your test code I ran into a few issues with the changes inserted for issue 2835.
https://github.com/jOOQ/jOOQ/commit/8875940e9d4ba5846ffaae6ce8735240ba62af09 The SQL is updated for the h2 test, but not the generated code. Either way, in PostgreSQL I have a table with the following columns: > > Table "public.example" > Column | Type | > Modifiers > > ------------------+--------------------------+------------------------------- > id | integer | not null default > nextval('example_id_seq'::regclass) > data | text | not null more_data | text | > check | boolean | not null default false In 3.2.0 if you generate the record and run: ExampleRecord exampleRecord = new ExampleRecord(); exampleRecord.setId(42); // Because I'm running integration tests and am crazy that way... exampleRecord.setData("text"); exampleRecord.store(); The select statement is: insert into "public"." example" ("id", "data", "more_data", "check") values (42, 'text') returning "public"."example"."id" In 3.2.2 the select statement is: insert into "public"." example" ("id", "data", "more_data", "check") values (42, 'text', null, null) returning "public"."example"."id" I stepped through the store call while running against the 3.2.2 code to determine if I could see where the change came from, but was unable to do so. I am going to continue looking at it, but figured I would ask if you or anyone had noticed this issue. Thanks, Jason -- 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.
