Compilation error in generated code when global object references conflict with schema names

[lukaseder]

The following simple DDL script can't be used as a source of code generation in jOOQ:

CREATE SCHEMA tables;
CREATE SCHEMA sequences;
CREATE SCHEMA domains;
CREATE SCHEMA keys;

CREATE TABLE tables.t (i int);
CREATE SEQUENCE sequences.s;
CREATE DOMAIN domains.d AS int; 
CREATE TABLE keys.t (i int, CONSTRAINT pk_t PRIMARY KEY (i));

The global object references generated this way will conflict with the schema names. The schema class is generated first, and then overwritten by the global object references class, leading to compilation errors in generated tables, for example, which reference the schema:

    @Override
    public Schema getSchema() {
        return aliased() ? null : Tables.TABLES; // Tables.TABLES does not exist
    }

The solution is to disambiguate the global object references class name in GeneratorStrategy::getGlobalReferencesJavaClassName, etc.

Affected global references files include:

• Domains
• Indexes
• Links
• Keys
• UDTs
• Queues
• Routines
• Sequences
• Tables
• Triggers

[lukaseder]

Fixed in versions

• 3.19.0
• 3.18.6 (Compilation error in generated code when global object references conflict with schema names - Merge [#15383] #15385)
• 3.17.15 (Compilation error in generated code when global object references conflict with schema names - Merge [#15383] #15386)
• 3.16.21 (Compilation error in generated code when global object references conflict with schema names - Merge [#15383] #15387)