summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/testing/assertions.py
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2012-10-04 13:50:36 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2012-10-04 13:50:36 -0400
commit1c3e3225521647cc843a633e34ed84e1ca4e797a (patch)
treef844e59c46b8df996c77e27f65dd6840ce1e49ed /lib/sqlalchemy/testing/assertions.py
parentf3e12698fbf03bc7c11a90f6d78d2b2a5efa70fd (diff)
downloadsqlalchemy-1c3e3225521647cc843a633e34ed84e1ca4e797a.tar.gz
- [feature] The Session will produce warnings
when unsupported methods are used inside the "execute" portion of the flush. These are the familiar methods add(), delete(), etc. as well as collection and related-object manipulations, as called within mapper-level flush events like after_insert(), after_update(), etc. It's been prominently documented for a long time that SQLAlchemy cannot guarantee results when the Session is manipulated within the execution of the flush plan, however users are still doing it, so now there's a warning. Maybe someday the Session will be enhanced to support these operations inside of the flush, but for now, results can't be guaranteed.
Diffstat (limited to 'lib/sqlalchemy/testing/assertions.py')
0 files changed, 0 insertions, 0 deletions