Christian Beikov

I tried your sample and noticed that the `quarkus-blaze-persistence-bom` refers to an old version of Blaze-Persistence. Upgrading to the latest version fixes the issue. ```xml com.blazebit blaze-persistence-entity-view-processor-jakarta 1.6.16 com.blazebit blaze-persistence-integration-hibernate-6.2...

Closing in favor of https://github.com/hibernate/hibernate-orm/pull/10093

Please change the Jira key of the tests from `HHH-12770` and the commit message from `HHH-00000` to `HHH-19214`.

Merging this is fine IMO, but AFAICT, JDK 26 simply has a bug in the ClassFile API, so it might be worth reporting this.

> You have mentioned two options: 1. GaussDB reuse code of PostgreSQL and 2. Not testging GaussDB in CI. If I follow option 1, and I think I can't follow...

Please, just try to reuse as much code as possible instead of copying code. For example, apparently you implement the same string format for structures/array like PostgreSQL since `GaussDBAbstractStructuredJdbcType` is...

End-users shouldn't interact with these types directly, so I hardly think that when you extend these types, it will imply anything. I understand your point, but you can still copy...

To be very clear, I'm not talking about reusing such glue classes like `PostgreSQLArrayJdbcTypeConstructor` and `OracleXmlArrayJdbcTypeConstructor` that you brought up. I'm talking about copying 500+ line classes for no good...

This change is not totally correct. If you use bytecode enhancement, lazy loading will occur on the first access to the field of the association.

It looks like this test here tests the scenario you're describing: https://github.com/hibernate/hibernate-orm/blob/main/hibernate-core/src/test/java/org/hibernate/orm/test/bytecode/enhancement/lazy/LazyToOneJoinOnNonPrimaryKeyColumnTest.java