Hi all,
I have a small problem with liquibase. I don’t know what I did wrong and at what point, but liquibase keeps insisting on dropping and adding a small subset of fkc’s (foreign key constraint) in my project.
Apparently everytime I alter the model, somehow the changes get stored somewhere for liquibase to find out what has changed and generate new changelog files. It is not based on a fresh analysis of the model but on a “hardwritting” of the model modification info. Because If I alter the model and then alter it back to what it was, two changesets are generated.
My problem is that I must have altered something in a way that whenever I start my project, liquibase automatically generates changesets that I don’t want to either execute nor store in changelog files. See a screenshot where this is illustrated.
Also I have the problem that I have recently introduced changes but can’t only execute the changeset that affects the database in the way I need. The other ones keep related to the failed fkc’s keep appearing no matter what I do (although I have let them be run on an attempt that they aren’t prompted anymore, but they keep being included everytime I start the app).
That’s why I think there has to be somewhere where I can delete a file and solve the problem.
Another possible solution I have come up with is to delete the whole changelog directory and try that liquibase generates a new changelog based on the current state of the model. Is it possible to do a fresh restart of the changelog files?. I know I would have to delete as well the databasechangelog table in the db. If this worked I think I would prefer this solution. Has anyone tried it?
Any ideas?
Thanks in advance for your help.
Regards.
Carlos.