Good point. Probably best to still run it against your real database type before a release.
I did get a version of my test data running on h2 but found them to run in the same time it took to run them aginst mysql. It seemed surprising. I'll keep looking into it. Nathan On Jan 16, 2009, at 10:44 AM, "petar" <peat...@yahoo.de> wrote: > > 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
