Re: [Liquibase-user] SQL for liquibase tables

2009-04-06 Thread Sven Haiges
(10)"); >> >> >> >> And >> >> >> >> return new CreateTableStatement(“databasechangeloglock”) >> >> .addPrimaryKeyColumn("ID", "INT", null, null, new >> NotNullConstraint()) >> >>

Re: [Liquibase-user] SQL for liquibase tables

2009-04-03 Thread Voxland, Nathan
OCKEDBY", "VARCHAR(255)"); You should be able to figure out the exact sql from that even if you don’t know java. Nathan From: Sven Haiges [mailto:hansam...@yahoo.de] Sent: Friday, April 03, 2009 5:12 PM To: liquibase-user@lists.sourceforge.net Subject: [Liquibase-user] SQL for liquibase tab

Re: [Liquibase-user] SQL for liquibase tables

2009-04-03 Thread Sven Haiges
quot;LOCKGRANTED", getDateTimeType()) > > .addColumn("LOCKEDBY", "VARCHAR(255)"); > > > > You should be able to figure out the exact sql from that even if you don’t > know java. > > > > Nathan > > > > *From:* Sven H

Re: [Liquibase-user] SQL for liquibase tables

2009-04-03 Thread Voxland, Nathan
Type(), new NotNullConstraint()) .addColumn("LOCKGRANTED", getDateTimeType()) .addColumn("LOCKEDBY", "VARCHAR(255)"); You should be able to figure out the exact sql from that even if you don't know java. Nathan From

[Liquibase-user] SQL for liquibase tables

2009-04-03 Thread Sven Haiges
Hi, I am brand new to liquibase and like what I exerienced so far. We would like to use liquibase for an existing project and the way we choose to migrate to using liquibase is have liquibase generate the SQL for us (updateSQL command). This works fine, but here is one little thing we don't under