Timeline for SSDT - Deprecated table trigger preventing publish
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 28, 2018 at 18:04 | comment | added | CasualFisher | I get that, but what do they hate more. Production that’s out of sync with the codebase or manually running a script to bring it back into line? You could even store the script in the SSDT project (and not add it to the build), name the file after a ticket reference and put a comment within the file explaining its existence. | |
| Aug 27, 2018 at 17:14 | comment | added | Elaskanator | Integration really hates doing that sort of thing, so I'd prefer an alternative. | |
| Aug 27, 2018 at 17:12 | history | edited | Elaskanator | CC BY-SA 4.0 |
added 91 characters in body
|
| Aug 27, 2018 at 16:24 | answer | added | Josh Darnell | timeline score: 1 | |
| Aug 25, 2018 at 21:29 | comment | added | CasualFisher | Why not remove the offending object manually? | |
| Aug 24, 2018 at 22:33 | history | asked | Elaskanator | CC BY-SA 4.0 |