[lug] MySQL work queue problem

Jason Vallery jason at vallery.net
Fri Oct 6 15:49:47 MDT 2006

InnoDB is fully ACID compliant, so if correct is what you are after it is
defiantly the type of table engine that you want.  The app I am working on
right now isn't particularly sensitive to referential integrity and
rollback, so I'm not concerned if there are a few issues caused by my
choice.  Performance is defiantly what I am after in this case.


On 10/6/06, Evelyn Mitchell <efm at tummy.com> 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?
> This email is: [ ] actionable [x] fyi [ ] social
> Response needed: [ ] yes [x] up to you [ ] no
> Time-sensitive: [ ] immediate [x] soon [ ] none
> --
> Regards,                    tummy.com, ltd
> Evelyn Mitchell             Linux Consulting since 1995
> efm at tummy.com               Senior System and Network Administrators
>                             http://www.tummy.com/
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20061006/aae68112/attachment.html>

More information about the LUG mailing list