Quoting Gábor Hojtsy <gabor@hojtsy.hu>:
On Nov 6, 2007 12:19 PM, Karoly Negyesi <karoly@negyesi.net> wrote:
Today marks the end of explicit database locks issued by Drupal core. Thanks to David Strauss who helped me getting rid of them by patching cache_set and variable_set in http://drupal.org/node/55516 .
Now, do we want to keep db_lock_table ? In Drupal 6, likely yes. In Drupal 7? The question makes sense even if go over to PDO.
Note that the installer still checks for LOCK permissions in the database. Now that we see some contrib modules use it, should we remove the LOCK check or should we keep it?
IMO the contrib module shouldn't depend on core to make sure that its requirements are met. However, it would be nice for core to provide methods to check the requirement exists. Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/