rzo1 opened a new pull request, #298: URL: https://github.com/apache/openjpa/pull/298
https://issues.apache.org/jira/browse/OPENJPA-2944 The exact case of the ticket (a UUID with a direct `AttributeConverter<UUID, String>`) already works on master since OPENJPA-2940/OPENJPA-3020. What remained: the database type `Y` of a converter was only found when a class in its superclass chain implemented `AttributeConverter` with concrete type arguments. A converter that extends a generic base class, or implements an interface extending `AttributeConverter`, resolved to `Object`; its attribute was mapped as a serialized BLOB (BYTEA on PostgreSQL), and such an auto-apply converter was not registered at all. - Converter type arguments are resolved through the whole type hierarchy; the auto-apply scan uses the same resolution, also for parameterized attribute types. - The repository warns when an auto-apply converter replaces another for the same type. New `TestConvertedColumnType` checks the column types through `DatabaseMetaData`; conversion/convert/external tests pass on Derby and PostgreSQL 18. **Still in progress (draft):** this changes the schema of existing applications on upgrade, so the change will be guarded by an `openjpa.Compatibility` flag and documented in the migration considerations and in an Upgrade Notes section of the release notes. CI: the TCK and Databases workflows were started on this branch; this PR stays a draft until both pass. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
