DSLContext.newRecord(Table) could throw NPEs if NULL values aren't acceptable, effectively requiring to call DSLContext.newRecord(Table, Object), instead.Potential additional work, out of scope for now: Compilation error in generated code when combining, and #14003.No default constructor should be available? KotlinGenerator shouldn't generate public default constructor if non-nullable attributes are generated on records #14002.Tasks for records / POJOs / interfaces non-null attributes With this choice, TableField references would still always be nullable, only records and/or POJOs are affected, as they're mostly used with SELECT * projections of single tables (no joins) But it would be a user choice, just like the !! operator. only nullable types are T?, the true positives, but non-nullable types, which are generated as T, would produce false negatives because they can still be null after an outer join, a union, etc.).
0 Comments
Leave a Reply. |