Hi Ben, In generated source code, jOOQ uses whatever is reported from the INFORMATION_SCHEMA. Unless there is some subtle bug in jOOQ-Meta, there might be a flag which influences the content of INFORMATION_SCHEMA.TABLES to report upper-cased table names instead of lower-cased ones.
By default, jOOQ identifiers are always considered case-sensitive. Your best choice to enforce case-insensitivity is by using RenderNameStyle as you mentioned in your other mail. Cheers Lukas 2013/8/9 Ben Hood <[email protected]> > Hi all, > > I'm working with Postgres 9.2 and I'm running into some issues with > the SQL JOOQ generates. > > JOOQ generates statements such as > > select * FROM "THINGS" AS "A" > > However the out of the box settings for Postgres render this statement > invalid to the upper/lower case differentiation rules. > > So if I change the DDL to be quoted upper case, i.e. > > create table "THINGS" ( ...); > > then the above SQL will be valid. > > I was wondering if there is a way to control the the upper/lower case > SQL generation in JOOQ. Forcing lower case quoting seems like it would > do the trick. > > Or do real Postgres pros know a switch that you can flip in the > database to make table names case insensitive? > > Cheers, > > Ben > > -- > 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/groups/opt_out. > > > -- 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/groups/opt_out.
