[development] The dawn of DB locks

[Larry Garfield]

I think you mean the dusk of DB locks, chx. :-)

In any case, yay.  I would recommend leaving db_lock_table() in place, as we 
can't guarantee that there will never be a case where a lock is needed; just 
that we've found workarounds for all of core's use-cases and many contribs'.  
Instead, I'd modify the docs for it to say "this is bad for performance, 
there's usually other ways like A, B, C, don't use this unless you really 
have to."

On Tuesday 06 November 2007, Karoly Negyesi wrote:
> Hi,
>
> 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.
>
> Regards,
>
> NK


-- 
Larry Garfield			AIM: LOLG42
larry at garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of 
exclusive property, it is the action of the thinking power called an idea, 
which an individual may exclusively possess as long as he keeps it to 
himself; but the moment it is divulged, it forces itself into the possession 
of every one, and the receiver cannot dispossess himself of it."  -- Thomas 
Jefferson