[
https://issues.apache.org/jira/browse/OPENJPA-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18141837#comment-18141837
]
ASF subversion and git services commented on OPENJPA-2944:
----------------------------------------------------------
Commit e9d0a152df0525724182242d905a6e760cf1bb70 in openjpa's branch
refs/heads/OPENJPA-2944 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=e9d0a152d ]
[OPENJPA-2944] Restore the 4.1.x converter type resolution with
ResolveConverterTypeHierarchy=false
Resolving the type arguments of an AttributeConverter through its whole type
hierarchy changes the mapping of existing applications: an attribute whose
converter declares its database type through a generic superclass or an
interface extending AttributeConverter moves from a serialized BLOB (BYTEA on
PostgreSQL) to a column of the converter's database type, and such autoApply
converters, as well as those of a parameterized attribute type, are now
registered.
The new Compatibility option ResolveConverterTypeHierarchy (default true)
restores the previous resolution for both the column type and the autoApply
registration when set to false. The warning about competing autoApply
converters is kept either way.
The change is described in the migration considerations and in a new
Upgrade Notes section of the release notes.
> Inconsistent column type conversion when using AttributeConverter
> -----------------------------------------------------------------
>
> Key: OPENJPA-2944
> URL: https://issues.apache.org/jira/browse/OPENJPA-2944
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 4.1.0
> Environment: Postgresql
> Reporter: Guenter Windsperger
> Priority: Minor
>
> When using an AttributeConverter the resulting expression is always of type
> `bytea` instead of the respective declared converter type e.g. bigint for
> Long.
> This can be observed with the existing Test `TestExternalValues`, where both
> UUID properties, one converted with the custom Externalizer API, the other
> with the standard Converter API, produce different column types.
> I am happy to provide some PR if someone could point me to the potential root
> cause.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
