A new topic, 'Extending Add|DropForeignKeyConstraintChange & Add|DropForeignKeyConstraintStmt', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=201.new#newThe text of the topic is shown below:
I'm trying to modify the the Add/DropForeignKeyConstraintChange classes for SQL Server to add cascading referential integrity (e.g. ON DELETE SET NULL) to the referenced table as a Trigger instead of as part of the constraint as per the discussion in my previous thread. Is it possible to extend these classes in 1.9.5 and supply my sub-classes of these to the Liquibase change factory without modifying the Liquibase source? If not, is it possible to do this in 2.0? Should I consider trying this using the RC version of 2.0?
Thanks!
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user
