]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- the 'expire' option on query.update() has been renamed to 'fetch', thus matching
authorMike Bayer <mike_mp@zzzcomputing.com>
Sun, 25 Jan 2009 00:48:15 +0000 (00:48 +0000)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sun, 25 Jan 2009 00:48:15 +0000 (00:48 +0000)
commita0c4060adfc2b6fc5c258ec29a878ea7fed98a52
treec40902b7272d1e25d2c20e832654c29061c89f31
parent68a733ecf51c154c9454ad3930a8bb54483e8ab2
- the 'expire' option on query.update() has been renamed to 'fetch', thus matching
that of query.delete()
- query.update() and query.delete() both default to 'evaluate' for the synchronize
strategy.
- the 'synchronize' strategy for update() and delete() raises an error on failure.
There is no implicit fallback onto "fetch".   Failure of evaluation is based
on the structure of criteria, so success/failure is deterministic based on
code structure.
06CHANGES [new file with mode: 0644]
lib/sqlalchemy/orm/query.py
test/orm/query.py