jOOQ 3.17 has added support for client side computed columns: https://github.com/jOOQ/jOOQ/issues/9879
A special case of these computed columns are audit columns, which will also be supported out of the box in jOOQ 3.17: https://github.com/jOOQ/jOOQ/issues/1592 On Friday, July 27, 2012 at 12:36:18 PM UTC+2 Lukas Eder wrote: > Optimistic locking has been implemented for jOOQ 2.5.0. > https://github.com/jOOQ/jOOQ/issues/1596 > > It will feature: > > - A flag in Settings to activate optimistic locking. Not everyone will > want to profit from this feature. For backwards-compatibility, > optimistic locking is deactivated by default > - No new methods are added. Optimistic locking is implemented in > UpdatableRecord.store() and UpdatableRecord.delete(), as well as > TableRecord.storeUsing() and TableRecord.deleteUsing() > - A new <recordVersionFields/> and <recordTimestampFields/> code > generator configuration properties have been added. These fields allow > for specifying regular expressions similar to <includes/> and > <excludes/> for matching table column names that are to be treated as > auto-generated version/timestamp columns. A table can have version > and/or timestamp columns. store() will always increment those values > on INSERT and UPDATE statements. store() and delete() will check those > values in the executed UPDATE / DELETE's WHERE clauses if the > previously mentioned Settings property is set. This is implemented > according to Sergey Epik's suggestion in this thread here. > - Without any specific code generation configuration, optimistic > locking is implemented trivially by issuing an additional SELECT .. > FOR UPDATE prior to the actual UPDATE or DELETE statement. This > additional statement is used to compare record values in Java. This is > implemented according to Ryan How's suggestion in this thread: > https://groups.google.com/d/topic/jooq-user/bGUYxeNd5X0/discussion > - These new features do not affect regular INSERT / UPDATE / DELETE > statements created from a Factory > - I am currently evaluating whether these new features should affect > Factory.batchStore(), and how > > Currently, "version" and "timestamp" values are generated by jOOQ in > Java. More sophisticated "version" types and generation > implementations may be added later, on demand (for instance, generate > "version" values from a sequence, or from any arbitrary Field<?> > expression. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/fcc3f87c-8fb3-42dc-9b1b-e4cc9dc7cfd8n%40googlegroups.com.
