Activity overview
Latest activity by adriancearnau
I think I can replicate this problem easily.
Every time I reorder the columns in a table with triggers and then commit a migration script with the modifications, the table definition SQL file gets modified and includes the same triggers twice.
If there are also trigger modifications caught in the migration script, the table definition file ends up containing both the previous and the current trigger definitions.
This is quite a nasty regression, I haven't had this problem in previous versions of SQL Source Control. Any idea where I could report this bug properly?
By the way, thanks a lot for the Ctrl+Shift tip, didn't know I can access the working base folder like that, always had to rummage through AppData before. / comments
I think I can replicate this problem easily.
Every time I reorder the columns in a table with triggers and then commit a migration script with the modifications, the table definition SQL file gets ...