]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Integrate new Result into ORM query
authorMike Bayer <mike_mp@zzzcomputing.com>
Fri, 24 Apr 2020 19:34:19 +0000 (15:34 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sat, 2 May 2020 15:18:13 +0000 (11:18 -0400)
commitbbf644862ab05734d153d74abf59aa3492278563
tree0a563147603ff2906422ed1b07e9f5f03e7584c8
parent7acf9af1ce74a0bda4c4d29af7da543b5c42b3f8
Integrate new Result into ORM query

The next step in the 2.0 ORM changes is to have the
ORM integrate with the new Result object fully.

this patch uses Result to represent ORM objects rather
than lists.  public API to get at this Result is not
added yet.   dogpile.cache and horizontal sharding
recipe/extensions have small adjustments to accommodate
this change.

Callcounts have fluctuated, some slightly better and
some slightly worse.  A few have gone up by a bit,
however as the codebase is still in flux it is anticipated
there will be some performance gains later on as
ORM fetching is refined to no longer need to accommodate
for extensive aliasing.   The addition of caching
will then change the entire story.

References: #5087
References: #4395

Change-Id: If1a23824ffb77d8d58cf2338cf35dd6b5963b17f
examples/dogpile_caching/caching_query.py
lib/sqlalchemy/ext/baked.py
lib/sqlalchemy/ext/horizontal_shard.py
lib/sqlalchemy/orm/loading.py
lib/sqlalchemy/orm/query.py
lib/sqlalchemy/orm/strategies.py
test/ext/test_baked.py
test/ext/test_horizontal_shard.py
test/orm/test_loading.py
test/orm/test_query.py
test/profiles.txt