If it is actually expanded outside the engine, is there an issue of it not being atomic?
Seems like some other thread could slip in and change the data such that the last step(s)
hit a conflict.
Rick James
MySQL Geeks - Consulting & Review
> -----Original Message-----
> From: Sergei Golubchik [mailto:serg@stripped]
> Sent: Monday, August 11, 2008 12:25 AM
> To: Krunal Bauskar
> Cc: internals@stripped
> Subject: Re: Can we disable REPLACE stmt in MySQL if SE can't
> support it ?
>
> Hi!
>
> On Aug 11, Krunal Bauskar wrote:
> > - Is there a way to disable REPLACE stmt if SE can't support it.
> > REPLACE internally is expanded as sequence of write,
> delete, update
> > row and so disabling directly at SE API level doesn't
> look feasible.
>
> Yes, it does not.
> Why you engine cannot support REPLACE if it's internally expanded as
> sequence of write, delete, update row ?
>
> Regards / Mit vielen Grüssen,
> Sergei
>
> --
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Sergei Golubchik <serg@stripped>
> / /|_/ / // /\ \/ /_/ / /__ Principal Software
> Engineer/Server Architect
> /_/ /_/\_, /___/\___\_\___/ Sun Microsystems GmbH, HRB
> München 161028
> <___/ Sonnenallee 1, 85551
> Kirchheim-Heimstetten
> Geschäftsführer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
> Vorsitzender des Aufsichtsrates: Martin Häring
>
> --
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe:
> http://lists.mysql.com/internals?unsub=1
>
>
