You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/04/18 10:21:15 UTC

[jira] Updated: (OPENJPA-221) DerbyDictionary doesn't describe a working mapping for char fields.

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

David Jencks updated OPENJPA-221:
---------------------------------

    Attachment: OPENJPA-221.patch

This patch results in a working mapping from a char field to a CHAR column.  I also added some comments to the defaults in DBDictionary that I hope are correct and helpful.

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