September 23, 2016 at 4:39 am
As the output a message of the parser in the query result window? :unsure:
(a small nit-pick...) 😉
September 23, 2016 at 6:16 am
TomThomson (9/22/2016)
Good interesting question.I rather dislike SQL Server's lumping together of multiple cascade paths and cascade cycles; it shouldn't be forcing us to use triggers in all cases where there can be multiple cascade paths. I'm perfectly happy for it to refuse to handle cascade cycles because I think a that it's potentially possible to obtain different results according to what order updates and/or deletions take place, but I would prefer to see it hadling multiple cycle-free cascade in cases where it's easy to detect (from the metadata) that different resuts can't be produced by different operation orders (as in the example in this case).
Agreed. I dislike cascading to begin with, but won't support multiple paths. I especially dislike cascade delete.
September 29, 2016 at 6:11 am
Great question, thanks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 3 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply