You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This support request re-appears all the time: #15246
jOOQ's code generator generates nullable properties for columns that are both NOT NULL and have a DEFAULT or IDENTITY expression or some other means of allowing NULLon write. The fact that the property is non-nullable on read isn't sufficient to add a nullability guarantee in generated code. Users may want to support null values when inserting the record, and in that case, the null value is supposed to apply the DEFAULT (given the NOT NULL constraint prevents actually storing the NULL value).
This support request re-appears all the time:
#15246
jOOQ's code generator generates nullable properties for columns that are both
NOT NULL
and have aDEFAULT
orIDENTITY
expression or some other means of allowingNULL
on write. The fact that the property is non-nullable on read isn't sufficient to add a nullability guarantee in generated code. Users may want to supportnull
values when inserting the record, and in that case, thenull
value is supposed to apply theDEFAULT
(given theNOT NULL
constraint prevents actually storing theNULL
value).What makes perfect sense after thinking about it a bit more thoroughly seems wrong and/or annoying at first, at the least, it is surprising. Adding additional documentation to this section would help:
https://www.jooq.org/doc/latest/manual/code-generation/kotlingenerator/
The text was updated successfully, but these errors were encountered: