Re: Issue with multiple schemas not being generated (or deleted) when one is using outputSchemaToDefault true

I've just merged a new improvement that fixes this issue to jOOQ 3.8.5: - https://github.com/jOOQ/jOOQ/issues/5556 (improvement) - https://github.com/jOOQ/jOOQ/issues/5593 (bug) I'm hoping to release 3.8.5 tomorrow. Thanks, Lukas Am Mittwoch, 19. Oktober 2016 10:22:06 UTC+2 schrieb Lukas Eder:

Re: Issue with multiple schemas not being generated (or deleted) when one is using outputSchemaToDefault true

It's Q3/Q4 2016. I would really like to get JSR 310 (java.time) API support for TIMESTAMP WITH TIME ZONE data types in this release - it's a feature that many users have requested for quite a while... This means that 3.9 might be taking another month or two. I'm planning to release 3.8.5 this

Re: Issue with multiple schemas not being generated (or deleted) when one is using outputSchemaToDefault true

No problem, Lukas. Thanks for getting back to me. Is there an estimated release date for 3.9.0? Cheers, Kai On Mon, Oct 17, 2016 at 12:43 PM, Lukas Eder wrote: > I'm sorry for the delay. This appears to be a bug in the code generator. > I've registered an issue for this:

Re: Issue with multiple schemas not being generated (or deleted) when one is using outputSchemaToDefault true

I'm sorry for the delay. This appears to be a bug in the code generator. I've registered an issue for this: https://github.com/jOOQ/jOOQ/issues/5593 Thank you very much for reporting. A workaround could be perhaps running two separate code generation runs and merging the contents into the same

Re: Issue with multiple schemas not being generated (or deleted) when one is using outputSchemaToDefault true

Bump. Anyone have any ideas? On Tuesday, October 11, 2016 at 3:33:49 PM UTC-6, Kai Waldron wrote: > > Using Jooq version 3.8.4: > > Scenario for this is a jooq.xml that has a the following generator snippet: > > > org.jooq.util.JavaGenerator > > >