Comments
Sort by recent activity
Thank you, Evan. It's useful to know that this is a known behavior and that there is a probable workaround. I checked the script for the table in the repository but the DISABLE TRIGGER statement was in there.
I thought I would experiment a little by enabling the trigger in the database directly. The change was picked up and properly committed. When I then disabled the trigger, the issue reoccurred where the change keeps being detected for commit. / comments
Thank you, Evan. It's useful to know that this is a known behavior and that there is a probable workaround. I checked the script for the table in the repository but the DISABLE TRIGGER statement wa...