[drupal-devel] [feature] Change LOCK in db_next_id (MySQL)

Dries drupal-devel at drupal.org
Sun May 1 21:34:33 UTC 2005

Issue status update for http://drupal.org/node/21439

 Project:      Drupal
 Version:      4.6.0
 Component:    base system
 Category:     feature requests
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  tostinni
 Updated by:   Dries
 Status:       patch

I wrote a mail to drupal-devel about making MySQL 4 a requirement.  If
we agree to drop support for MySQL 3, the proposed patch might improve
performance too (although it will not be noticable).


Previous comments:

April 27, 2005 - 21:12 : tostinni

Attachment: http://drupal.org/files/issues/database.mysql.inc.patch (600 bytes)

Some ISP doesn't let user to make LOCK on tables (I'm thinking at
free.fr a famous french free ISP).
This patch provide another method to lock tables using SELECT ... FOR


April 27, 2005 - 22:10 : chx

Hm , tostinni is this applicable for MyISAM tables? I thought select for
update is for InnoDB.


April 28, 2005 - 00:03 : tostinni

Well, MySQL doc [1] doesn't specify that it's restricted to MyISAM
tables type, in fact I try this in a DB I got at free.fr which restrict
tables types to MyISAM and it worked.

So I guess it's fine ;)
[1] http://dev.mysql.com/doc/mysql/en/select.html


May 1, 2005 - 19:15 : Dries

SELECT ... FOR UPDATE uses row-level locking which requires MySQL 4 as
far as I know.  The syntax is ANSI SQL though.  Are you using MySQL 3
or MySQL 4?

More information about the drupal-devel mailing list