summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authormike bayer <mike_mp@zzzcomputing.com>2021-08-18 04:58:45 +0000
committerGerrit Code Review <gerrit@ci3.zzzcomputing.com>2021-08-18 04:58:45 +0000
commitbaaa988b381ce09def215b9889681092d2046cdc (patch)
tree0b5daa8323002fed32d7199f82f9b0f51c81d5df /doc
parentf454499c5dd1449eed3b59a7eca54744bcfe9f3d (diff)
parent29485026e9ea6500ea451b1d4a6f66795a02428d (diff)
downloadsqlalchemy-baaa988b381ce09def215b9889681092d2046cdc.tar.gz
Merge "send user defined options from the current query"
Diffstat (limited to 'doc')
-rw-r--r--doc/build/changelog/unreleased_14/6887.rst21
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/build/changelog/unreleased_14/6887.rst b/doc/build/changelog/unreleased_14/6887.rst
new file mode 100644
index 000000000..8992dccba
--- /dev/null
+++ b/doc/build/changelog/unreleased_14/6887.rst
@@ -0,0 +1,21 @@
+.. change::
+ :tags: bug, orm
+ :tickets: 6887
+
+ Revised the means by which the
+ :attr:`_orm.ORMExecuteState.user_defined_options` accessor receives
+ :class:`_orm.UserDefinedOption` and related option objects from the
+ context, with particular emphasis on the "selectinload" on the loader
+ strategy where this previously was not working; other strategies did not
+ have this problem. The objects that are associated with the current query
+ being executed, and not that of a query being cached, are now propagated
+ unconditionally. This essentially separates them out from the "loader
+ strategy" options which are explicitly associated with the compiled state
+ of a query and need to be used in relation to the cached query.
+
+ The effect of this fix is that a user-defined option, such as those used
+ by the dogpile.caching example as well as for other recipes such as
+ defining a "shard id" for the horizontal sharing extension, will be
+ correctly propagated to eager and lazy loaders regardless of whether
+ a cached query was ultimately invoked.
+