Lukas Eder

Closing this as won't fix as I couldn't manage to get this change right in kotlin.

As a workaround, maybe it's simpler to just offer plain SQL `TableElement` and `CustomTableElement` types where users can implement their own syntax for inclusion in `CREATE TABLE` and `ALTER TABLE`...

This issue still persists: - https://feedback.azure.com/d365community/idea/341a56e4-02f6-ec11-a81b-6045bd796569 I've also now found this one: - https://feedback.azure.com/d365community/idea/60b7b3a2-526a-ed11-a81b-000d3ae49307 This stuff doesn't really seem to work...

I'm closing this PR. While https://github.com/jOOQ/jOOQ/issues/7014 will be implemented eventually, the suggested implementation is probably not going to be the one that will make it.

Is there anything we could do from our side to make this work more easily? E.g. we could provide free license keys to help you test this integration, if you're...

Great, I'll be in touch by email

> One of the criteria we have on quarkiverse hub is that the extensions are open source which includes their build [...] but this is the first case we have...

> > How does this work for commercial JDBC drivers? > > the one we test in community are all available in maven central, even oracle's. But you said "open...

... would be a great thing to do anyway, to regression test jOOQ in a quarkus context on our side :)

It certainly works for me for now.