Re: [Liquibase-user] CLOB vs. LONGTEXT

2009-03-16 Thread Voxland, Nathan
A couple options: - You could create a subclass of the MySqlDatabase class and override the getClobType() method. You can pass the databaseClassName into liquibase. - You could also specify the type as a parameter: column type=${clobType}/ and then pass the value into liquibase. I would think

Re: [Liquibase-user] CLOB vs. LONGTEXT

2009-03-16 Thread David C. Hicks
Cool. Thanks, Nathan. Voxland, Nathan wrote: A couple options: - You could create a subclass of the MySqlDatabase class and override the getClobType() method. You can pass the databaseClassName into liquibase. - You could also specify the type as a parameter: column type=${clobType}/ and

Re: [Liquibase-user] Calling Liquibase API with contexts.

2009-03-16 Thread Ben Wolfe
There is an attribute or element you can add to changeSets for putting in other valid checksums. You put the old changeSet checksum in there that the production system has already, then make your edit to the changeSet. Now all future checks use a new checksum and the current production

Re: [Liquibase-user] Calling Liquibase API with contexts.

2009-03-16 Thread David C. Hicks
I'm afraid I didn't keep a copy of it, but it amounted to a problem within Hibernate/JPA where the autoincrement ID of one of my objects could not be read back after the object was persisted. This was long after the call to Liquibase had completed and the test case was into the