We don't use the autocreate feature... That is what liquibase is for :) I think you're best option is to override the h2 and/or oracle Database class (can pass your classname to liquibase as a parameter) and override the method that converts the datatype string in your changelog file to the one to pass to the database. I'm on vacation currently so I don't know what it is off hand. Let me know if you can't find it or are not quite sure what to do.
Nathan On Jan 18, 2009, at 8:51 PM, "Clarence Ho" <clare...@clarenceh.com> wrote: > Hi Peter and Nathan, > > I didn't have the problem you mentioned, since my company has a DB > design > standard that all table and column names should not exceed 30 > characters. > Are you using auto-create table feature in Hibernate? > > I guess you can override the table name being created by Hibernate, > to make > it work in both databases. > > In my case, I run the same changelog against H2 for unit tests and > Oracle > for other cases. I use the tag "DBMS Type" to indicate the DB that I > am > using. > > But as I said, my major problem is of data type (in Oracle, I use > "Timestamp > with local time zone", while H2 not support). I really think changelog > parameters is not the best solution for it. > > Hi Nathan, what do you think about this? > > Clarence > > > -------------------------------------------------- > From: "petar" <peat...@yahoo.de> > Sent: Saturday, January 17, 2009 12:43 AM > To: <liquibase-user@lists.sourceforge.net> > Subject: Re: [Liquibase-user] Liquibase - different column type > fordifferentdatabase vendor > >> >> Hi Nathan and Clarence, >> >> one issue I encountered: running h2 was fine, but oracle has a >> limited >> column name length (32 or so). >> And so although all tests pass with h2 the fail on production. The >> reason: >> join tables auto-created from hibernate were too long.. >> >> Regards, >> Peter. >> >> -- >> View this message in context: >> http://www.nabble.com/Liquibase---different-column-type-for-different-database-vendor-tp21326128p21503445.html >> Sent from the LiquiBase - User mailing list archive at Nabble.com. >> >> >> --- >> --- >> --- >> --------------------------------------------------------------------- >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> Liquibase-user mailing list >> Liquibase-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/liquibase-user >> > > > --- > --- > --- > --------------------------------------------------------------------- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Liquibase-user mailing list > Liquibase-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/liquibase-user ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user
