On 4 syys, 17:53, lucky <[email protected]> wrote: > *E) Use locking with SELECT query* > According tohttp://dev.mysql.com/doc/refman/5.5/en/innodb-consistent-read.html > > If you want to see the “freshest” state of the database, use either the > READ COMMITTED isolation level or a locking read: > SELECT * FROM t LOCK IN SHARE MODE;
If I recall correctly the problem with this approach is that while you can read the object from the DB, you can't save it back. UPDATE and SELECT in .save() doesn't see the row, INSERT results in integrity error. I might remember this wrong, so this is something to test when trying this approach. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
