If you in the generator configuration haven't set <records>false</records>,
then the jOOQ code generator should automatically be generating
UpdatableRecordImpl subclasses for all your tables. You should then be able
to use these classes instead of your CustomRecord subclasses.
I hope this answers your question.
On Wednesday, September 11, 2019 at 9:54:07 PM UTC+2, Max Kremer wrote:
No specific reason other than we haven't really needed to.
Yes, we write our own TableImpl subclasses by hand but there are only 3-4
of them. Our application is mostly doing analytics and we rely on JOOQ as a
DSL for building queries (creating reusable chunks of SQL and combining
them, manipulating them etc...). So far JOOQ has been perfect for that. We
haven't had the requirement to do typical CRUD operations on
records/objects.... until now.
I looked at the UpdatableRecordImpl class but the internal docs say *"This
type is for JOOQ INTERNAL USE only. Do not reference directly"*
On Thursday, September 12, 2019 at 10:10:29 AM UTC-4, Knut Wannheden wrote:
> records/objects.... until now.
> I looked at the UpdatableRecordImpl class but the internal docs say *"This
> type is for JOOQ INTERNAL USE only. Do not reference directly"*
When upgrading to a new jOOQ version I would recommend that you do run the
code generator and at least compare its output to your own hand-maintained
The TableImpl class has the same disclaimer in the Javadoc and both classes
are also annotated as @Internal. But extending either of these classes
(like the code generator does) is legitimate. But please note that, since
these are internal classes, the API could break in backwards incompatible
ways in a future minor release. This is not a problem if you are using the
code generator, as its API remains backwards compatible and it will always
generate classes matching TableImpl and UpdatableRecordImpl.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].