Humm I'll check on Monday when I go back to work.
David C. Hicks wrote:
> It looks as if you have checked your "target" folder into your source
> control system. You should not do that. "target" is a throw-away
> directory where Maven builds artifacts.
> Other things that are often found but sho
There is a tag, but it does require the
constraint name because that is how most database (including hsql)
structure their sql. HSQL is ALTER TABLE DROP CONSTRAINT
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 const
Marco, we are currently using an approach that could make your dba happier:
every release, we make an export of the database and use it as a "seed" for the
next release. This way, we avoid having to re-execute all of the past
changeSets everytime we need a fresh database. I guess this export/im
It looks as if you have checked your "target" folder into your source
control system. You should not do that. "target" is a throw-away
directory where Maven builds artifacts.
Other things that are often found but should not be included in source are:
.project - the Eclipse project file
.
Unable to update source folders mpi-database;
java.lang.IllegalArgumentException: Element not found:
///target/classes/liquibase
Any ideas?
--
___
Liquibase-user mail
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 di
