[lug] MySQL work queue problem

Zan Lynx zlynx at acm.org
Fri Oct 6 17:36:53 MDT 2006

On Fri, 2006-10-06 at 15:02 -0600, Evelyn Mitchell wrote:
> * On 2006-10-06 14:32 George Sexton <gsexton at mhsoftware.com> wrote:
> > 
> > If a second thread tries the update statement, the row count will be 0 
> > because the status field has already been changed. That's assuming that 
> > MySQL can actually atomically update records...
> I though that MySQL achieved some of their performance at the risk of data
> integrity. Namely, that they don't support Atomic changes with rollback,
> or anything close to full database ACID. Postgres, does support full ACID,
> by the way. 
> Do you want fast or correct, or just how important is this data to your
> users?

That's old information now.  MySQL's current versions support a variety
of table backends, some of which implement full ACID compliance.  You
can still choose fast and loose if you want it though.

Zan Lynx <zlynx at acm.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20061006/d955e868/attachment.pgp>

More information about the LUG mailing list