There is a <dropUniqueConstraint> tag, but it does require the constraint name because that is how most database (including hsql) structure their sql. HSQL is ALTER TABLE <tablename> DROP CONSTRAINT <constraintname>
Without a constraint name, I don't think there is much you can do. I would say you should always give a unique name to your constraints so you can get a handle on them later. You may need to use the custom refactoring class support in liquibase to write something that will interrogate the hsql information_schema for the unique constraint name for a given table and column, then drop it. Nathan -----Original Message----- From: Koichi Tsunoda [mailto:ichikoo...@hotmail.com] Sent: Thursday, April 02, 2009 4:14 PM To: liquibase-user@lists.sourceforge.net Subject: [Liquibase-user] Dropping a unique constraint for HSQLDB vialiquibase Hello all, If the underlying DB that I'm using is MySQL, I can remove the unique constraint on a column by doing a drop index in the migration file. However, when I switch to using HSQLDB, drop index doesn't work. I suppose it doesn't work because in HSQLDB, I'm supposed to do something different to drop the unique constraint. I looked around and I could not find a way to drop a unique constraint via liquibase yet. Also, when the unique constraint was first created, a name wasn't given to it, so I cannot use a drop unique constraint by name either. Does anyone now how to do this? Thanks! Koichi ------------------------------------------------------------------------ ------ _______________________________________________ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user ------------------------------------------------------------------------------ _______________________________________________ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user
