[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6717) oracle does not have a boolean type

[Steve Ebersole (JIRA)]

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

Steve Ebersole commented on HHH-6717:
-------------------------------------

The problem here is that of legacy compatibility.  We need this to do whatever Hibernate used to do.  iirc Hibernate used to treat booleans as char-based.  If so, that is what we need to continue to do here now as well.  The concern is this: imagine an application has previously used Hibernate's schema export to generate a table for and entity with a boolean.  If we now change the behavior of how that stores/retrieves the boolean value we have introduced a mismatch and broken that application.  

I totally agree that what you describe is the appropriate behaviour.  However we just need to cater to this legacy case.  Seems like a flag is the most appropriate solution.

> oracle does not have a boolean type
> -----------------------------------
>
>                 Key: HHH-6717
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6717
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>            Reporter: Strong Liu
>            Assignee: Strong Liu
>             Fix For: 4.0.0.next
>
>
> now Dialect has mapped Types.BOOLEAN to 'boolean' by default, then we need change this in Oracle dialect to let it map to _char(1)_

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