Hi Alex Thank you for your detailed report!
> [...] Another observation is that with > jOOQ 2.3.1 only classes generated specifying > <inputSchema>public</inputSchema> works out of the box. I will try to reproduce that. > I know that one of jOOQ goals is to abstract from the db vendor but is there > a better way to deal with my scenario? Postgres is pretty standard SQL in the way it organises databases, catalogs, schemata and tables, so jOOQ should generally work as expected. > What if I generate classes for the whole db1 setting no <inputSchema>? You can do that with jOOQ 2.3.x since #1286. jOOQ will then generate a sub-package for each schema in the db1 database. > Forcing the schema rendering on the Sch1Factory passing a > new Settings().withRenderSchema(true) has no effect in my case. You don't have to use Sch1Factory. In fact, one of the features of the generated [Schema-Name]Factory classes is the fact that it will omit referencing [Schema-Name] in rendered SQL. Have you tried using just PostgresFactory or Factory instead? Cheers Lukas
