Lukas Eder

Well, lacking integration test cases for such edge cases thus far, I can (regrettably) confirm that what you're expecting is what's currently being generated for RDBMS that don't have an...

The PostgreSQL specific inconsistency only appears when: - PostgreSQL 15 is configured - `RETURNING` is present (i.e. `Settings.returnIdentityOnUpdatableRecord` is set, which is the default, so by default, we keep generating...

Thanks for your suggestion. There's currently no public API, only internal API that can be used to attach comments to `Field` expressions, which I won't document here. The problem is...

I will address this now in jOOQ 3.17. A new `ColumnElement` type will allow for enough forward compatibility with such additional "flags" and "attributes" that can be attached to `Field`...

Will finally implement this in jOOQ 3.18. The suggested syntax will merely be syntax sugar for using this new API: https://github.com/jOOQ/jOOQ/issues/14510

I'm not sure yet about this particular syntax. Personally, I like the new API better, with the explicit `COMMENT` "keyword". The API is added via #14510, and https://github.com/jOOQ/jOOQ/issues/14512 adds the...

#14512 is implemented in jOOQ 3.18. I'll look into implementing `ALTER TABLE .. ADD .. COMMENT` support as well, see: https://github.com/jOOQ/jOOQ/issues/14513

Thanks a lot for your report and your patience. I'm afraid, the notification email must have slipped by. This looks like a duplicate of https://github.com/jOOQ/jOOQ/issues/12472, which also documents workarounds.

Related issue: - https://github.com/jOOQ/jOOQ/issues/17561

This is indeed a duplicate of https://github.com/jOOQ/jOOQ/issues/12472