On 13 Mar 2007, at 13:44, JamesDR wrote:
With what you've provided us: You can not prevent this. You are
running
in a transaction which is isolated from any others.
But doesn't that isolation provide atomicity, i.e. the first
transaction to commit will act as if all of its component queries
occurred before the first query of the second one, even if they are
actually issued in an overlapping order? Consequently, the first
query of the second transaction in my example should not succeed in
finding anything. Or are transactions not atomic this way??
Marcus
--
Marcus Bointon
Synchromedia Limited: Creators of http://www.smartmessages.net/
UK resellers of [EMAIL PROTECTED] CRM solutions
[EMAIL PROTECTED] | http://www.synchromedia.co.uk/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
