[
https://issues.apache.org/jira/browse/OPENJPA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489791
]
David Jencks commented on OPENJPA-221:
--------------------------------------
I'm not in a position to easily modify the applications in question (they are
in the tck) but if I only set storeCharsAsNumbers=false in code then I got a
lot of openjpa unit test errors complaining that it couldn't create the table
for AllFieldTypes, something about CHAR(255). changing the other property
fixed that. If I turned off the unit tests then openjpa worked fine with
preexisting derby tables with a CHAR column for the char field. Is this enough
info?
> DerbyDictionary doesn't describe a working mapping for char fields.
> -------------------------------------------------------------------
>
> Key: OPENJPA-221
> URL: https://issues.apache.org/jira/browse/OPENJPA-221
> Project: OpenJPA
> Issue Type: Bug
> Components: sql
> Affects Versions: 0.9.7
> Reporter: David Jencks
> Attachments: OPENJPA-221.patch
>
>
> If a class has a char field mapped to CHAR or CHAR(1) in a derby database,
> the derby dictionary sets up a mapping to an integer column which doesn't
> work. openjpa tries to store e.g. the string "97" for the char 'a' which
> results in a truncation error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
