Added to TODO:
* Add MERGE command that does UPDATE, or on failure, INSERT
---------------------------------------------------------------------------
Christopher Kings-Lynne wrote:
> >>Except you can keep trying and trying without the outermost transaction
> >>failing.
> >
> > But that won't provide the necessary next key locking you mentioned in
> > your first email, will it?
>
> No, but since I can loop an infinite number of times until either the
> update or insert works, I don't need next key locking.
>
> BTW, the reference in MySQL:
>
> http://dev.mysql.com/doc/mysql/en/REPLACE.html
>
> Hmm...no refernce to next key locking. Maybe that's an Innodb thing...
>
> Anyway, you can see how they've implemented their algorithm.
>
> Here is docs on the DB2 merge command from which the standard was derived:
>
> http://databasejournal.com/features/db2/article.php/10896_3322041_2
>
> Chris
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
