On 02/11/2010 10:24 PM, John Firebaugh wrote:
I was the original author of the OUTPUT code and the performance
improvement is important for my use case.
What's the compatibility issue you are encountering? Perhaps we can
come up with a more targeted change.
An insert trigger on any table will fail when using the OUTPUT clause
(as used by Sequel), which is how I've been bitten. Looking at the SQL
Server documentation there are quite a few other cases that are
incompatible with the OUTPUT clause.
I'm certainly not suggesting that the feature is removed and I
appreciate that there are cases where insert heavy applications need
that bit of extra speed. I'm just suggesting a change in the default
behaviour as a principle of least surprise. The OUTPUT clause can be
enabled when you need the speed and when you *know* that you won't get a
problem with the OUTPUT clause restrictions.
I would have thought that far more people would have been bitten by the
incompatibilities in the OUTPUT clause than get issues with insert
performance. Apparently I'm in the minority and most people have simpler
databases than me.
I'm OK with it at the moment as I can work round the trigger issue for
now, but that may not always be the case.
Regards,
Gary.
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sequel-talk?hl=en.
