[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6705) SQL datatypes for booleans not being handled correctly

[Lukasz Antoniak (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43962#comment-43962 ] 

Lukasz Antoniak commented on HHH-6705:
--------------------------------------

In my opinion there is a little bug in Oracle dialects. Oracle RDBMS does not support (in any version) BOOLEAN column type. BOOLEAN can be legally used only in PL/SQL stored procedure. I did not know that Hibernate manages mapping of Boolean/boolean properties. I've been always extending {{org.hibernate.type.CharBooleanType}} to create a custom type.

So, should Boolean be mapped to NUMBER(1,0) or CHAR(1)? In my opinion NUMBER(1,0) is more universal, because acronyms for 'Yes' and 'No' can differ in various languages. Teradata dialect also uses 'BYTEINT'.

> SQL datatypes for booleans not being handled correctly
> ------------------------------------------------------
>
>                 Key: HHH-6705
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6705
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 4.0.0.CR4
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 4.0.0.next
>
>         Attachments: hhh-6705-server.log, hhh-6705.war, hhh-6705.war.zip
>
>
> Perhaps due to changes for metamodel... 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira