openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-221) DerbyDictionary doesn't describe a working mapping for char fields.
Date Wed, 18 Apr 2007 14:39:15 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489761
] 

Patrick Linskey commented on OPENJPA-221:
-----------------------------------------

What happens if, without your patch, you set the DBDictionary 'StoreCharsAsNumbers' property
to false?

<persistence>
  <persistence-unit name="...">
    ...
    <properties>
      <property name="openjpa.jdbc.DBDictionary" value="StoreCharsAsNumbers=false"/>
    </properties>
  </persistence-unit>
</persistence>

> 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.


Mime
View raw message