Home Forums Article Discussions Article Discussions by Author Discuss content posted by Dwain Camps A Hazard of Using the SQL Update Statement RE: A Hazard of Using the SQL Update Statement

  • September 9, 2013 at 1:28 am

    #1648450

    natalie.ignatieva (9/9/2013)

    Jeff Moden (9/8/2013)

    I, however, do not consider the fact that it won’t give you an error for an attempted multiple-update on a single row a fault. Nay. I consider it to be a feature! I actually hate Oracle for trying to be so dutiful as to thwart my attempts to get something done by producing errors for things that I actually want to do.

    I totally agree with you about that it's a feature and it's not a hazard.

    Prior to the introduction of MERGE I'd have agreed with this - we learned to ensure that multiple source rows for a target row had the same source value. Now though? It's inconsistent - and changing the behaviour of UPDATE to match the strictness of MERGE would break too much legacy code.

    “Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw

    For fast, accurate and documented assistance in answering your questions, please read this article.
    Understanding and using APPLY, (I) and (II) Paul White
    Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden