Re: [Sqlalchemy-tickets] [sqlalchemy] #814: with_lockmode() doesn't allow db-native lockmodes
Brought to you by:
zzzeek
|
From: sqlalchemy <mi...@zz...> - 2014-01-22 00:30:24
|
#814: with_lockmode() doesn't allow db-native lockmodes
-----------------------------------+----------------------------------
Reporter: jek | Owner: zzzeek
Type: defect | Status: closed
Priority: low | Milestone: 0.x.xx
Component: orm | Severity: minor - half an hour
Resolution: fixed | Keywords: orm
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: awaiting triage => completed/closed
Comment:
with_lockmode() has been superseded by with_for_update(), which is
available with the same calling interface on both select() and Query. It
accepts "read", "nowait" as flags as well as "of". so we've exposed the
SQL level detail of "FOR UPDATE" and there's not really any translation
anymore. with_lockmode() itself translates the string codes into those
flags which are then interpreted by the dialect.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/814#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|