Hi Denis, The easiest way to work around this would be to use Settings.renderCatalog to turn off the generation of catalog names.: http://www.jooq.org/javadoc/latest/org/jooq/conf/Settings.html#renderCatalog
Unfortunately, we've added catalog support in jOOQ 3.8 without supporting code generator catalog mappings, which will be supported in jOOQ 3.9 only: https://github.com/jOOQ/jOOQ/issues/4794 I hope this helps for the time being, Best Regards, Lukas 2016-10-16 11:19 GMT+02:00 Denis Miorandi <[email protected]>: > Hi Lukas, > > I'm moving from jooq 3.7 to 3.8. Actually catalog names are different from > dev, test, and production servers (DB can be SQLSERVER or POSTGRES) > On 3.7 my code work on all environments cause no catalog information is > printed on queries, so connection string address to right catalog. > Moving to 3.8 I suspect that generated code (on test db) will not work on > production db (different catalog). > > How can I face this? Is it possible configure jooq to work without print > fully qualified (catalog part) names? Or may I pass catalog name as > parameters to configuration? > Are there any other solutions to this? > > Tks > > Denis > > -- > 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.
