[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463?page=c...
]
Adrian Moos edited comment on HHH-6463 at 8/31/11 6:39 AM:
-----------------------------------------------------------
Using the following dialect solves the schema generation issue for me:
{code}
public class WorkingOracle11gDialect extends Oracle10gDialect {
public WorkingOracle11gDialect() {
registerColumnType(java.sql.Types.BOOLEAN, "Number(1,0)");
}
}
{code}
was (Author: adrian.moos):
Using the following dialect solves the schema generation issue for me:
/**
* An Oracle11gDialect that actually works with Hibernate 4 / Oracle 11g.
*/
public class WorkingOracle11gDialect extends Oracle10gDialect {
public WorkingOracle11gDialect() {
registerColumnType(java.sql.Types.BOOLEAN, "Number(1,0)");
}
}
hbm2ddl and Oracle DB: Found: number, expected: boolean
-------------------------------------------------------
Key: HHH-6463
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 4.0.0.Beta1
Reporter: Thomas
As described in this forum topic:
https://forum.hibernate.org/viewtopic.php?f=1&t=1011905&start=0
Since version 4 Hibernate (hbm2ddl) cannot map a boolean field in a JPA entity to a
column with type number(1,0) in Oracle DB.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira