Hi John, > 1. since Oracle only allows upper-case schema names, you could use > upper(schema_name) in your code and thus avoid this problem (basically treat > it as if schema name is case-insensitive). This could be done for all other > object names in Oracle as well.
I wasn't aware of this, but you're right, as the documentation suggests: http://docs.oracle.com/cd/B28359_01/server.111/b28286/sql_elements008.htm So it might make sense to support case-insensitive <inputSchema> filters in the source code generator. This would also have to apply for the <outputSchema>, though. At least for Oracle. I'll file this as feature request #1418: https://sourceforge.net/apps/trac/jooq/ticket/1418 > 2. if the code generation creates no table objects, you could output the > query that likely caused this (in my case, the one that used the lower-case > schema name) as informational (INFO) message to user. Since this would > generally be an unexpected result, it would be helpful for newbies to see > some output that helps them solve the problem. You're probably right. Then again, the includes / excludes filters may cause this as well, and there are other reasons, too. I'll think about this: https://sourceforge.net/apps/trac/jooq/ticket/1419 Cheers Lukas
