[drupal-devel] LOCK vs. SELECT FOR UPDATE

Gerhard Killesreiter killesreiter at physik.uni-freiburg.de
Wed Sep 28 21:50:50 UTC 2005

On Wed, 28 Sep 2005, Robert Douglass wrote:

> Moshe Weitzman wrote:
> > As for Gerhard's original question, it would certainly be nice to get
> > rid of the requirement on LOCK TABLES permission. That has bit me before
> > shared web hosts. Maybe we should use different locking technique
> > depending on the table type or permission level of the DB user.
> >
> That bit me on  a managed server (strato.de) One would think that if
> you've got the entire server, managed or not, that you could count on
> these features being there. I had to move the project to a root server
> because of LOCK TABLES.

I've searched a bit about when and why we introduced locking in the first


It still does no explain why we need(ed?) to have the ID before the
commit. Does anybody recall this?


More information about the drupal-devel mailing list