For the record, this was introduced in jOOQ 2.1.0: https://github.com/jOOQ/jOOQ/issues/1212
There is now a very similar regression in jOOQ 3.8.0 where table names may collide with schema names: https://github.com/jOOQ/jOOQ/issues/5268 Am Freitag, 13. Mai 2016 09:37:39 UTC+2 schrieb Lukas Eder: > > Hi Samir, > > This is intentional. There is already a table literal DATE_FORMAT, which > would collide with the column literal DATE_FORMAT. > > You can use jOOQ's generator strategies to rename either the table > literal, or the column literal: > > - Programmatic: > http://www.jooq.org/doc/latest/manual/code-generation/codegen-generatorstrategy > - Configurative: > http://www.jooq.org/doc/latest/manual/code-generation/codegen-matcherstrategy > > Hope this helps, > Lukas > > 2016-05-13 1:34 GMT+02:00 Samir Faci <[email protected]>: > >> I'm not sure if this is a bug or was brought up before (I hope not). >> >> But if I have a table named >> >> DATE_FORMAT >> >> Which also includes a column named DATE_FORMAT >> >> Then the autogen code seems to add an underscore to the column name. >> >> For example: >> >> List<String> supportedDateFormats = dslContext. >> selectDistinct(DATE_FORMAT.DATE_FORMAT_) >> .from(DATE_FORMAT) >> .orderBy(DATE_FORMAT.DATE_FORMAT_) >> .fetchInto(String.class); >> >> >> >> is this intentional? Or is there something I can do on my end >> configuration wise to avoid this pattern >> >> >> -- >> Thank you >> Samir Faci >> >> -- >> 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/d/optout. >> > > -- 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/d/optout.
