delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/persistence.py, branch rel_1_2 github.com: zzzeek/sqlalchemy.git Run search and replace of symbolic module names 2020-04-14T17:23:30+00:00 Mike Bayer mike_mp@zzzcomputing.com 2020-04-14T17:23:30+00:00 0961297e70c066772aecb514eb8aa53531716de8 Replaces a wide array of Sphinx-relative doc references with an abbreviated absolute form now supported by zzzeeksphinx. Change-Id: I94bffcc3f37885ffdde6238767224296339698a2 
Replaces a wide array of Sphinx-relative doc references
with an abbreviated absolute form now supported by
zzzeeksphinx.

Change-Id: I94bffcc3f37885ffdde6238767224296339698a2
Fix many spell glitches 2019-01-25T20:17:47+00:00 Lele Gaifax lele@metapensiero.it 2019-01-14T16:26:33+00:00 a127185e09866d0027528d111e86ec0667cd2719 This affects mostly docstrings, except in orm/events.py::dispose_collection() where one parameter gets renamed: given that the method is empty, it seemed reasonable to me to fix that too. Closes: #4440 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4440 Pull-request-sha: 779ed75acb6142e1f1daac467b5b14134529bb4b Change-Id: Ic0553fe97853054b09c2453af76d96363de6eb0e (cherry picked from commit 66e88d30a86fc37e2eaf7367e988ced3834e3250) 
This affects mostly docstrings, except in orm/events.py::dispose_collection()
where one parameter gets renamed: given that the method is
empty, it seemed reasonable to me to fix that too.

Closes: #4440
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4440
Pull-request-sha: 779ed75acb6142e1f1daac467b5b14134529bb4b

Change-Id: Ic0553fe97853054b09c2453af76d96363de6eb0e
(cherry picked from commit 66e88d30a86fc37e2eaf7367e988ced3834e3250)
Add QueryEvents before_compile_update / before_compile_delete 2019-01-23T03:24:19+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-23T02:49:07+00:00 0491d7b4130e7e81d66f4426533ba44ea8bbcf18 Added new event hooks :meth:`.QueryEvents.before_compile_update` and :meth:`.QueryEvents.before_compile_delete` which complement :meth:`.QueryEvents.before_compile` in the case of the :meth:`.Query.update` and :meth:`.Query.delete` methods. Fixes: #4461 Change-Id: I47884f0e1f07d7e62870c2a918b15f917f9245ab (cherry picked from commit bd735eba637cbf2c157046f72dc795a8b2b803e7) 
Added new event hooks :meth:`.QueryEvents.before_compile_update` and
:meth:`.QueryEvents.before_compile_delete` which complement
:meth:`.QueryEvents.before_compile` in the case of the :meth:`.Query.update`
and :meth:`.Query.delete` methods.

Fixes: #4461
Change-Id: I47884f0e1f07d7e62870c2a918b15f917f9245ab
(cherry picked from commit bd735eba637cbf2c157046f72dc795a8b2b803e7)
happy new year 2019-01-11T15:07:20+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-11T15:06:10+00:00 3cfc3c2faaf6465fef75242a17961e4cfeee405b Change-Id: I6a71f4924d046cf306961c58dffccf21e9c03911 (cherry picked from commit 6f270fb0e344016ce526e0a1ecb3e3de9ffd1e3b) 
Change-Id: I6a71f4924d046cf306961c58dffccf21e9c03911
(cherry picked from commit 6f270fb0e344016ce526e0a1ecb3e3de9ffd1e3b)
Post black reformatting 2019-01-06T16:51:20+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-06T06:32:41+00:00 18abd47af32136b3c94a8a787905286d279181fa Applied on top of a pure run of black -l 79 in I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9, this set of changes resolves all remaining flake8 conditions for those codes we have enabled in setup.cfg. Included are resolutions for all remaining flake8 issues including shadowed builtins, long lines, import order, unused imports, duplicate imports, and docstring issues. Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe 
Applied on top of a pure run of black -l 79 in
I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9,  this set of changes
resolves all remaining flake8 conditions for those codes
we have enabled in setup.cfg.

Included are resolutions for all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe
Run black -l 79 against all source files 2019-01-06T06:31:01+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-06T06:31:01+00:00 580139598f846f1ce4e2bcfb522ec51d1829c580 This is a straight reformat run using black as is, with no edits applied at all. The black run will format code consistently, however in some cases that are prevalent in SQLAlchemy code it produces too-long lines. The too-long lines will be resolved in the following commit that will resolve all remaining flake8 issues including shadowed builtins, long lines, import order, unused imports, duplicate imports, and docstring issues. Change-Id: I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9 
This is a straight reformat run using black as is, with no edits
applied at all.

The black run will format code consistently, however in
some cases that are prevalent in SQLAlchemy code it produces
too-long lines.   The too-long lines will be resolved in the
following commit that will resolve all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9
Use attr keys when testing bulk update params for primary key 2018-11-02T01:54:37+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-11-02T01:53:18+00:00 50170e62b32d118373d839965bb08546b4a248e9 Fixed bug in :meth:`.Session.bulk_update_mappings` where alternate mapped attribute names would result in the primary key column of the UPDATE statement being included in the SET clause, as well as the WHERE clause; while usually harmless, for SQL Server this can raise an error due to the IDENTITY column. This is a continuation of the same bug that was fixed in :ticket:`.3849`, where testing was insufficient to catch this additional flaw. Fixes: #4357 Change-Id: Iead058c0465dfa31c5b8a8780769278b7000acc8 (cherry picked from commit e991684a39fa9fae2628ce583e141b9aea99d856) 
Fixed bug in :meth:`.Session.bulk_update_mappings` where alternate mapped
attribute names would result in the primary key column of the UPDATE
statement being included in the SET clause, as well as the WHERE clause;
while usually harmless, for SQL Server this can raise an error due to the
IDENTITY column.  This is a continuation of the same bug that was fixed in
:ticket:`.3849`, where testing was insufficient to catch this additional
flaw.

Fixes: #4357
Change-Id: Iead058c0465dfa31c5b8a8780769278b7000acc8
(cherry picked from commit e991684a39fa9fae2628ce583e141b9aea99d856)
Don't run postfetch_post_update for a DELETE 2018-08-23T16:01:18+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-08-23T15:55:13+00:00 066c25ba892787cdac448e82ac77daf9174310f1 Fixed 1.2 regression caused by :ticket:`3472` where the handling of an "updated_at" style column within the context of a post-update operation would also occur for a row that is to be deleted following the update, meaning both that a column with a Python-side value generator would show the now-deleted value that was emitted for the UPDATE before the DELETE (which was not the previous behavor), as well as that a SQL- emitted value generator would have the attribute expired, meaning the previous value would be unreachable due to the row having been deleted and the object detached from the session.The "postfetch" logic that was added as part of :ticket:`3472` is now skipped entirely for an object that ultimately is to be deleted. Fixes: #4327 Change-Id: Ieac845348979df296bcf7e785c0353bdc6074220 (cherry picked from commit 1b5393db36a6c4353d41c7065b29a377d7c3b9b2) 
Fixed 1.2 regression caused by :ticket:`3472` where the handling of an
"updated_at" style column within the context of a post-update operation
would also occur for a row that is to be deleted following the update,
meaning both that a column with a Python-side value generator would show
the now-deleted value that was emitted for the UPDATE before the DELETE
(which was not the previous behavor), as well as that a SQL- emitted value
generator would have the attribute expired, meaning the previous value
would be unreachable due to the row having been deleted and the object
detached from the session.The "postfetch" logic that was added as part of
:ticket:`3472` is now skipped entirely for an object that ultimately is to
be deleted.

Fixes: #4327
Change-Id: Ieac845348979df296bcf7e785c0353bdc6074220
(cherry picked from commit 1b5393db36a6c4353d41c7065b29a377d7c3b9b2)
Ensure mapping has no version_id_generator when checking missing version_id 2018-02-22T16:36:34+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-02-21T16:16:09+00:00 8ab7c9639881e75eb93014438d30cc7208d3f796 Fixed 1.2 regression in ORM versioning feature where a mapping against a :func:`.select` or :func:`.alias` that also used a versioning column against the underlying table would fail due to the check added as part of :ticket:`3673`. See also #4194 and #4195 for related issues found regarding mapped selects and versioning. Change-Id: Ifabe9a5c8c1bfa72db5029faa7a5dbf71f0a7ca0 Fixes: #4193 
Fixed 1.2 regression in ORM versioning feature where a mapping against a
:func:`.select` or :func:`.alias` that also used a versioning column
against the underlying table would fail due to the check added as part of
:ticket:`3673`.

See also #4194 and #4195 for related issues found regarding
mapped selects and versioning.

Change-Id: Ifabe9a5c8c1bfa72db5029faa7a5dbf71f0a7ca0
Fixes: #4193
happy new year 2018-01-12T19:23:53+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-01-12T19:23:53+00:00 699272e4dcb9aa71ebbc0d9487fb6de82d3abc2b Change-Id: I3ef36bfd0cb0ba62b3123c8cf92370a43156cf8f 
Change-Id: I3ef36bfd0cb0ba62b3123c8cf92370a43156cf8f