Richard Lynch wrote:
[snip...]
> I think the idea is this:
>
> 1. LOCK TABLES invovled.
> 2. Get the current values for all records you are about to change.
> 3. Attempt to make changes.
> 4. If any of the attempted changes fails, change back the ones that
> succeded.*
you just can't relie on
> can someone explain me how to use LOCK TABLES to subtitute transactions?
>
> I don't seem to get how this is possible... and I really need this... I
> have a script that updates 4 tables at a time, and I have to be sure all
of
> them are updated, or NONE... I can only see this possible using
> c
can someone explain me how to use LOCK TABLES to subtitute transactions?
I don't seem to get how this is possible... and I really need this... I
have a script that updates 4 tables at a time, and I have to be sure all of
them are updated, or NONE... I can only see this possible using
commit/ro
3 matches
Mail list logo
