Trigger script without SETs produces invalid script #103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… added directly after the trigger definition with no new line.
…sn't tacked onto teh end of the definition when there are no SETs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If your database settings for ANSI_NULLS and QUOTED_IDENTIFIER are ON, then the SETs are not outputted in the script.
This is fine, but if your trigger definition does not have a new line at the end, then the ENABLE ends up being added straight onto the end of the definition, giving you e.g. "INSERTEDENABLE"
I have added a newline before the ENABLE keyword to guarantee that this can never happen.
If you'd like me to do something different, let me know.
Thanks