Issue Details (XML | Word | Printable)

Key: NUCRDBMS-636
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Vladimir Konkov
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus Store RDBMS

Pessimistic locking does not work with MS SQL Server

Created: 25/Jan/13 06:26 AM   Updated: 14/Feb/13 11:14 AM   Resolved: 14/Feb/13 11:14 AM
Component/s: None
Affects Version/s: 3.1.0.release, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.2.0.m1, 3.2.0.m2
Fix Version/s: 3.1.5, 3.2.0.m3

File Attachments: 1. Text File NUCRDBMS-636.patch (0.6 kB)

Environment: MacOS X, JDK 1.6

Datastore: Microsoft SQL Server, SapDB - MaxDB
Severity: Development


 Description  « Hide
MS SQL does not support FOR UPDATE syntax, instread row level locking is implemented as hint (WITH ...). MSSQLServerAdapter includes syntax, but that syntax not used in SQLStatement for implementing correct row level locking.
I've attach the patch. Please apply if its relevant.

PS: propably, SAPDB also affected by this bug.

Sort Order: Ascending order - Click to sort in descending order
Vladimir Konkov added a comment - 25/Jan/13 08:58 AM - edited
Bug affects only main table that declared after FROM clause, for joined tables row level locking worked fine.

Andy Jefferson added a comment - 25/Jan/13 09:38 AM
Thx. SVN trunk adds that now

Vladimir Konkov added a comment - 25/Jan/13 10:42 AM
Andy, thank you.
Please, can you include this patch in stable 3.1.x branch? Of couse, if that not contrary to project rules.

Andy Jefferson added a comment - 14/Feb/13 11:14 AM
Also now in branches/3.1