No option to exclude dependencies from schema model update

When I go to commit a change using Flyway Desktop, the "schema update" will almost always include extra artifacts that I did not choose. 

These are listed as dependencies, but due to my data model (many foreign keys) and a generous definition of "dependencies" (e.g., a stored procedure references a table, and another stored procedure references a table with a foreign key relationship to the first table, which apparently means both objects are going to be committed), I almost never actually want to commit these objects together. 

I can work around by only choosing some items in the "commit changes" window, but then I have a whole pile of other things sitting there waiting to be committed, and it's a huge pain.  My team's workflow is to hop back and forth between Visual Studio and Flyway, undoing and removing unwanted items before committing. 

Is there a way to "ignore dependencies" when saving changes to my schema model? 
Tagged:

Answers

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file