[jira] [Commented] (OPENJPA-2731) Problems with Boolean Representation with Postgres

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on OPENJPA-2731:
----------------------------------------------------------

Commit 1827923 from [~fyrewyld] in branch 'openjpa/branches/2.2.x'
[ https://svn.apache.org/r1827923 ]

OPENJPA-2731: Problems with Boolean Representation with Postgres

> Problems with Boolean Representation with Postgres
> --------------------------------------------------
>
>                 Key: OPENJPA-2731
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2731
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.2.2
>            Reporter: Jody Grassel
>            Assignee: Jody Grassel
>            Priority: Major
>              Labels: easyfix
>         Attachments: patch_2.2.x.txt
>
>
> OPENJPA-2558 addressed, in general, boolean representations on the database (native Boolean column types, as an int(0,1), as a string, as a char, etc), but had coverage gaps with respect to the supported platforms.  Postgres is one of those platforms.  Its dictionary class still overrode setBoolean(), but did not equally override getBoolean() which introduced a conflict.
> I'm proposing an update which removes the setBoolean() method from the Postgres dbdictionary, as well as adding the ability for a database platform to declare a default boolean representation type (preserving the INT10 default, but setting Postgres' to BooleanRepresentation in order to match what the schemagenerator for postgres creates).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)