delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/query.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
Document Query deduplication 2019-09-05T15:48:15+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-09-05T15:46:44+00:00 d57dadc08f9c07f640d3ac96ce0d402fdcb1c109 Users are frequently confused why count() does not return the same number as the number of objects returned by all(). While we continue to want to find a better solution to this problem, in the meantime this has never been clearly documented. Add an FAQ section with links from .count() , .all(), ORM tutorial. Change-Id: I6eff36b686ff6cdd55489036fc48a981bc47d5ee (cherry picked from commit 75c3950732a66ff7f4aca152653d6cb14eb9783c) 
Users are frequently confused why count() does not return the same
number as the number of objects returned by all().  While we continue
to want to find a better solution to this problem, in the meantime
this has never been clearly documented.  Add an FAQ section with
links from .count() , .all(), ORM tutorial.

Change-Id: I6eff36b686ff6cdd55489036fc48a981bc47d5ee
(cherry picked from commit 75c3950732a66ff7f4aca152653d6cb14eb9783c)
Add documentation for MySQL optimizer hints using prefix_with 2019-05-08T15:43:11+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-05-08T15:40:12+00:00 8f11e4222219405fd1e9941d11bde9c8f595ed2f Fixes: #4667 Change-Id: Iac3345319dc7c5a20bc7a6520492d2f341b64807 (cherry picked from commit c608c3f2f8af0e4cd9e2ffbd3b6f7f487e785282) 
Fixes: #4667
Change-Id: Iac3345319dc7c5a20bc7a6520492d2f341b64807
(cherry picked from commit c608c3f2f8af0e4cd9e2ffbd3b6f7f487e785282)
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)
Adapt single inh criteria more specifically 2019-01-18T04:15:04+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-18T01:08:10+00:00 6256b40d3f0699720d44fc6e4866ca00191f0851 Fixed issue where when using single-table inheritance in conjunction with a joined inheritance hierarchy that uses "with polymorphic" loading, the "single table criteria" for that single-table entity could get confused for that of other entities from the same hierarchy used in the same query.The adaption of the "single table criteria" is made more specific to the target entity to avoid it accidentally getting adapted to other tables in the query. Change-Id: Ia9f915a4b01e8bb9cee365c4c70e00c626f103c4 Fixes: #4454 (cherry picked from commit c8d7141c79829f36e123bf3e4be1721dd34aaeb4) 
Fixed issue where when using single-table inheritance in conjunction with a
joined inheritance hierarchy that uses "with polymorphic" loading, the
"single table criteria" for that single-table entity could get confused for
that of other entities from the same hierarchy used in the same query.The
adaption of the "single table criteria" is made more specific to the target
entity to avoid it accidentally getting adapted to other tables in the
query.

Change-Id: Ia9f915a4b01e8bb9cee365c4c70e00c626f103c4
Fixes: #4454
(cherry picked from commit c8d7141c79829f36e123bf3e4be1721dd34aaeb4)
Remove version directives for 0.6, 0.7, 0.8 2019-01-15T15:52:18+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-15T15:49:36+00:00 996eb2d4bf7dcff57e4d47d467e8252ced5fe13d - fix a few "seealso"s - ComparableProprerty's "superseded in 0.7" becomes deprecated in 0.7 Backport to currently maintained doc versions 1.2, 1.1 Change-Id: Ib1fcb2df8673dbe5c4ffc47f3896a60d1dfcb4b2 (cherry picked from commit 885f15a306efc4c907ca82fa13871992ee556466) 
- fix a few "seealso"s
- ComparableProprerty's "superseded in 0.7" becomes deprecated in 0.7

Backport to currently maintained doc versions 1.2, 1.1

Change-Id: Ib1fcb2df8673dbe5c4ffc47f3896a60d1dfcb4b2
(cherry picked from commit 885f15a306efc4c907ca82fa13871992ee556466)
use ..deprecated directive w/ version in all cases 2019-01-12T23:11:51+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-08T22:46:55+00:00 9db219665ab8fac776a1ce01f458887aea2996ee These changes should be ported from 1.3 back to 1.0 or possibly 0.9 to the extent they are relevant in each version. In 1.3 we hope to turn all deprecation documentation into warnings. (cherry picked from commit 77e9534673d58f2f4c33d16c0ed4e8671cea48b6) Change-Id: I205186cde161af9389af513a425c62ce90dd54d8 
These changes should be ported from 1.3 back to 1.0 or
possibly 0.9 to the extent they are relevant in each
version. In 1.3 we hope to turn all deprecation documentation
into warnings.

(cherry picked from commit 77e9534673d58f2f4c33d16c0ed4e8671cea48b6)
Change-Id: I205186cde161af9389af513a425c62ce90dd54d8
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