Compilation error in generated DAO code when visibility of a field is changed to private

[lukaseder]

There's a test that makes the visibility of a field private:

<forcedType>
    <visibilityModifier>PRIVATE</visibilityModifier>
    <includeExpression>VISIBILITY\.PRIVATE</includeExpression>
</forcedType>

That leads to a compilation error in the generated DAO, which refers to the columns as follows:

    /**
     * Fetch records that have <code>PRIVATE BETWEEN lowerInclusive AND
     * upperInclusive</code>
     */
    public List<org.jooq.codegen.test.visibility.db.tables.pojos.Visibility> fetchRangeOfPrivate(Integer lowerInclusive, Integer upperInclusive) {
        return fetchRange(Visibility.VISIBILITY.PRIVATE, lowerInclusive, upperInclusive);
    }

    /**
     * Fetch records that have <code>PRIVATE IN (values)</code>
     */
    public List<org.jooq.codegen.test.visibility.db.tables.pojos.Visibility> fetchByPrivate(Integer... values) {
        return fetch(Visibility.VISIBILITY.PRIVATE, values);
    }

We mustn't generate these utility methods if the visibility is non-public. If the visibility was package private or protected, we could still check if the DAO is in the same package as the table.

[lukaseder]

The feature has been introduced in jOOQ 3.17: #13432

[lukaseder]

Fixed in versions:

• 3.19.0
• 3.18.5 (Compilation error in generated DAO code when visibility of a field is changed to private - Merge [#15183] #15184)
• 3.17.14 (Compilation error in generated DAO code when visibility of a field is changed to private - Merge [#15183] #15185)