Timeline for Using XLOCK In SELECT Statements
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Apr 15, 2017 at 0:36 | comment | added | John L. | The sample snippet you provided perfectly solves the scenario I mentioned in the question. But I guess it wouldn't be possible to apply this approach if the scenario required more complex checks such as joins or operated on a range of rows, right? I checked the UPDLOCK and HOLDLOCK pattern you mentioned but as far as I understand, it does not prevent a read from other transactions. | |
| Apr 14, 2017 at 23:18 | history | answered | Joe Obbish | CC BY-SA 3.0 |