[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463?page=c... ] Scott Marlow commented on HHH-6463: ----------------------------------- issue https://issues.jboss.org/browse/AS7-1354 was reported against HHH-6463. I don't see why this issue is a blocker myself. I think that the hbm2ddl tool is meant for writing unit tests, not for creating your application database. I'm not arguing but just pointing out some additional facts about expectations for hbm2ddl. Also, I thought that hbm2ddl is part of Hibernate tools, not core. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463?page=c... ] Thomas commented on HHH-6463: ----------------------------- I think you're right, Scott. It's not a blocker for me. I use the hbm2ddl.auto=validate property to check my db schema against the jpa entities. This is useful to fail fast (when deploying a new version) when they both are not in sync. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463?page=c... ] Kos Kosta commented on HHH-6463: -------------------------------- Well its update, validate, create, create-drop <<< basicly anything you use for Domain Driven Development. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463?page=c... ] Scott Marlow commented on HHH-6463: ----------------------------------- I closed AS7-1354 as a duplicate of this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463?page=c... ] Adrian Moos edited comment on HHH-6463 at 8/31/11 6:37 AM: ----------------------------------------------------------- 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)"); } } 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)"); } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463?page=c... ] Mark Kempster commented on HHH-6463: ------------------------------------ This is reproducible by pointing the seam 3.1.0.Beta4 seam-booking example application at an oracle datasource (I used 10g) and altering the persistence.xml to make these two changes 1. <jta-data-source>java:jboss/datasources/OracleDS</jta-data-source> 2. <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/> I deployed this on as7.0.2.Final and see the following log entry (prettied up) HHH00389:Unsuccessful: create table Booking ( id number(19,0) not null, beds number(10,0) not null, checkinDate date, checkoutDate date, creditCardExpiryMonth number(10,0) not null, creditCardExpiryYear number(10,0) not null, creditCardName varchar2(70 char) not null, creditCardNumber varchar2(16 char) not null, creditCardType varchar2(255 char) not null, smoking boolean, <-- problem column hotel_id number(19,0) not null, user_username varchar2(15 char) not null, primary key (id)) It may not be a blocker use case, but I thought the seam example should deploy on as7 with oracle out of the box, as it does with hypersonic. The prior fix using hibernate's @Type doesn't appear to be available any more? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira