I'd rather not touch my generated classes at all, the thing is I didn't know about dirty flags so I was doing everything unaware of the issues this behavior may cause.
Thank you! On Friday, February 15, 2013 12:00:03 PM UTC+1, Lukas Eder wrote: > > > My DDL is the following: > > > > CREATE TABLE user_session > > ( > > id bigserial NOT NULL, > > id_user integer NOT NULL, > > ... > > ) > > > > > > What I was doing was get a custom type of object from a JSON, > deserialize it > > and then convert it into a Record. In the conversion step (MyObject --> > > Record) I didn't check for the null value on the PK (which is null when > the > > client wants to add a new object to the collection), never realizing > that by > > setting the value to null would set the flag of the column to dirty. I > > assumed that the operation was somewhat idempotent under all aspects. > Turns > > out I was wrong :). > > I see. Well, this issue has been discussed once or twice :-) > > It turns out that for me, the best option in the short run was to > expose the dirty flags to the outside of records, such that users can > at least explicitly influence this behaviour in jOOQ. > > Cheers > Lukas > -- 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.
