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

[Kai Waldron]

Using Jooq version 3.8.4:

Scenario for this is a jooq.xml that has a the following generator snippet:

   <generator>

        <name>org.jooq.util.JavaGenerator</name>

        <database>

            <name>org.jooq.util.postgres.PostgresDatabase</name>

            <schemata>

                <schema>

                    <inputSchema>master</inputSchema>

                    <outputSchema>master</outputSchema>

                </schema>

                <schema>

                    <inputSchema>model</inputSchema>

                    <outputSchemaToDefault>true</outputSchemaToDefault>

                </schema>

            </schemata>

      ...

   </generator>

Issue I'm seeing is when the "model" schema has outputSchemaToDefault set to true, the master schema gets generated (if I watch the file system), and then deleted. The "model" schema does get generated to the _ directory. 

If I comment out <outputSchemaToDefault>true</outputSchematoDefault> the master schema generates correctly and is not deleted, but then of course the model schema is now qualified with model..which we don't want. Any ideas on how to get this combination to play nicely together?

Thanks,

Kai

[Kai Waldron]

Bump. Anyone have any ideas?

[Lukas Eder]

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 directory using the Maven resources plugin, for instance...

Best Regards,

Lukas

--
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 jooq-user+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kai Waldron]

No problem, Lukas. Thanks for getting back to me.

Is there an estimated release date for 3.9.0?

Cheers,

Kai

--
You received this message because you are subscribed to a topic in the Google Groups "jOOQ User Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jooq-user/cWt_Jvo3-B0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jooq-user+unsubscribe@googlegroups.com.

[Lukas Eder]

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 week, though, so that fix could be available very soon already.

[Lukas Eder]

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