]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6033b07) | patch
- FOR UPDATE is emitted in the syntactically correct position
authorMike Bayer <mike_mp@zzzcomputing.com>
Thu, 27 May 2010 15:50:16 +0000 (11:50 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Thu, 27 May 2010 15:50:16 +0000 (11:50 -0400)
commit40c7db67b46fac0029f8caf7a53cbceb05a2324d
treee695096e217a76a7d5c889f7f0de25613f8d5ac0tree | snapshot
parent6033b074094d96f17640cc9ab8ea86e6de94927acommit | diff
- FOR UPDATE is emitted in the syntactically correct position
when limit/offset is used, i.e. the ROWNUM subquery.
However, Oracle can't really handle FOR UPDATE with ORDER BY
or with subqueries, so its still not very usable, but at
least SQLA gets the SQL past the Oracle parser.
[ticket:1815]
CHANGES diff | blob | blame | history
lib/sqlalchemy/dialects/oracle/base.py diff | blob | blame | history
test/dialect/test_oracle.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git