I have hundreds of foreign key constraints defined in changeSets that looks like this:
This works fine on the 2 databases I need to support (oracle + mssql). However, if I need to rollback this changeSet - LiquiBase fails on mssql as it is appending the " NOT FOR REPLICATION" option to the auto-generated DROP CONSTRAINT sql.
(I see the applyToRollback attribute should default to false).
I’m looking to extend the core LiquiBase to support my requirements, but am not sure which classes to extend to cater for the addForeignKey tags.
In an ideal world, I’d like to be able to define an extension that automatically handles my two mssql modifications (i.e. the replace and the append) - which classes would I extend to do this?
Alternatively, how do I stop LiquiBase appending the extra text to the auto-generated roll-back?