| List: | General Discussion | « Previous MessageNext Message » | |
| From: | (Hal | Date: | December 19 2011 7:58pm |
| Subject: | Re: UPDATE triggers with REPLACE statements | ||
| View as plain text | |||
>>>> 2011/12/19 11:30 -0800, Jim McNeely >>>>
In the MySQL documentation, we find this tantalizing statement:
"It is possible that in the case of a duplicate-key error, a storage engine may perform
the REPLACE as an update rather than a delete plus insert, but the semantics are the
same. There are no user-visible effects other than a possible difference in how the
storage engine increments Handler_xxx status variables."
<<<<<<<<
Well, try it--but beware of these statements: "the semantics are the same. There are no
user-visible effects other than a possible difference in how the storage engine
increments Handler_xxx status variables."
If accurate, the triggers are those of DELETE & INSERT, not UPDATE.
| Thread | ||
|---|---|---|
| • UPDATE triggers with REPLACE statements | Jim McNeely | 17 Dec |
| • Re: UPDATE triggers with REPLACE statements | hsv | 18 Dec |
| • Re: UPDATE triggers with REPLACE statements | Claudio Nanni | 18 Dec |
| • Re: UPDATE triggers with REPLACE statements | Jim McNeely | 19 Dec |
| • Re: UPDATE triggers with REPLACE statements | Jim McNeely | 19 Dec |
| • Re: UPDATE triggers with REPLACE statements | Claudio Nanni | 19 Dec |
| • Re: UPDATE triggers with REPLACE statements | Jim McNeely | 19 Dec |
| • Re: UPDATE triggers with REPLACE statements | hsv | 20 Dec |
| • Re: UPDATE triggers with REPLACE statements | hsv | 19 Dec |
| • Re: UPDATE triggers with REPLACE statements | Jim McNeely | 19 Dec |
| • Re: UPDATE triggers with REPLACE statements | hsv | 23 Jan |
