http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DC-984 Doctrine 1 <p>When using pessimistic locking as described in:</p> <p><a href="http://www.doctrine-project.org/projects/orm/1.2/docs/manual/component-overview:locking-manager:examples/zh" class="external-link">http://www.doctrine-project.org/projects/orm/1.2/docs/manual/component-overview:locking-manager:examples/zh</a></p> <p>the locking manager locks the entire table rather than the specific object. </p> <p>This should be clear from the attached patch which corrects the issue (assuming I have correctly interpreted the intention of pessimistic locking!).</p> <p>The current behavior will have worked as expected for users but it will have locked far more than was intended and may thus have affected performance.</p> <p>NB: I can confirm this works for non-composite keys but please review and test for composite keys as I have no such tables to hand.</p> Standard LAMP stack using current SVN from <a href="http://svn.doctrine-project.org/branches/1.2/lib/Doctrine/Locking/Manager">http://svn.doctrine-project.org/branches/1.2/lib/Doctrine/Locking/Manager</a> DC-984

Pessimistic locking locks entire table rather than record

Bug Major Open Unresolved Jonathan H. Wage Barry O'Donovan Wed, 16 Mar 2011 07:53:30 +0000 Thu, 13 Dec 2012 13:13:16 +0000 1.2.4 Transactions 1 2 <p>Folks - just wondering if anyone had a chance to look at this as, while not critical, it does appear to be a genuinely major performance issue.</p> <p>Duplicate with more information : <a href="http://www.doctrine-project.org/jira/browse/DC-185" class="external-link">http://www.doctrine-project.org/jira/browse/DC-185</a></p>