Re: update multiple rows continue past exceptions
From: jimmyb <jimmybrock_at_gmail.com>
Date: Sun, 13 Dec 2009 21:53:54 -0800 (PST)
Message-ID: <3b5f962c-e71f-4348-9669-82b2f8737a56_at_f20g2000prn.googlegroups.com>
On Dec 13, 4:21 pm, Steve Howard <stevedhow..._at_gmail.com> wrote:
> On Dec 12, 1:41 am, Mladen Gogala <gogala.mla..._at_gmail.com> wrote:
>
>
>
> > Why not simply use the merge statement?
>
> > --http://mgogala.byethost5.com
>
> This is a regular event in our shop. Our developers used to try to
> insert, and then handle the exception if it existed and update it. We
> cut our redo by a large factor when we asked them to switch to MERGE.
Date: Sun, 13 Dec 2009 21:53:54 -0800 (PST)
Message-ID: <3b5f962c-e71f-4348-9669-82b2f8737a56_at_f20g2000prn.googlegroups.com>
On Dec 13, 4:21 pm, Steve Howard <stevedhow..._at_gmail.com> wrote:
> On Dec 12, 1:41 am, Mladen Gogala <gogala.mla..._at_gmail.com> wrote:
>
>
>
> > Why not simply use the merge statement?
>
> > --http://mgogala.byethost5.com
>
> This is a regular event in our shop. Our developers used to try to
> insert, and then handle the exception if it existed and update it. We
> cut our redo by a large factor when we asked them to switch to MERGE.
They used to do an UPDATE when an exception was raised? That should be a bad coding practice in every shop, JMO. Received on Sun Dec 13 2009 - 23:53:54 CST