summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authormike bayer <mike_mp@zzzcomputing.com>2021-11-18 16:11:35 +0000
committerGerrit Code Review <gerrit@ci3.zzzcomputing.com>2021-11-18 16:11:35 +0000
commitc0b0bf8ab81ac966a8c5a428a45cddbafaaf6e18 (patch)
tree2b1e7c95d8c2f77cf7b387b95c32c3755ce3f680 /doc
parent958f902b1fc528fed0be550bc573545de47ed854 (diff)
parentb2df5be7ee8b5ee7ae67323b5018ca37bbf0ce2a (diff)
downloadsqlalchemy-c0b0bf8ab81ac966a8c5a428a45cddbafaaf6e18.tar.gz
Merge "Deprecate create_engine.implicit_returning" into main
Diffstat (limited to 'doc')
-rw-r--r--doc/build/changelog/unreleased_20/6962.rst28
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/build/changelog/unreleased_20/6962.rst b/doc/build/changelog/unreleased_20/6962.rst
new file mode 100644
index 000000000..fcc3c1997
--- /dev/null
+++ b/doc/build/changelog/unreleased_20/6962.rst
@@ -0,0 +1,28 @@
+.. change::
+ :tags: deprecations, engine
+ :tickets: 6962
+
+ The :paramref:`_sa.create_engine.implicit_returning` parameter is
+ deprecated on the :func:`_sa.create_engine` function only; the parameter
+ remains available on the :class:`_schema.Table` object. This parameter was
+ originally intended to enable the "implicit returning" feature of
+ SQLAlchemy when it was first developed and was not enabled by default.
+ Under modern use, there's no reason this parameter should be disabled, and
+ it has been observed to cause confusion as it degrades performance and
+ makes it more difficult for the ORM to retrieve recently inserted server
+ defaults. The parameter remains available on :class:`_schema.Table` to
+ specifically suit database-level edge cases which make RETURNING
+ infeasible, the sole example currently being SQL Server's limitation that
+ INSERT RETURNING may not be used on a table that has INSERT triggers on it.
+
+
+.. change::
+ :tags: bug, oracle
+ :tickets: 6962
+
+ Related to the deprecation for
+ :paramref:`_sa.create_engine.implicit_returning`, the "implicit_returning"
+ feature is now enabled for the Oracle dialect in all cases; previously, the
+ feature would be turned off when an Oracle 8/8i version were detected,
+ however online documentation indicates both versions support the same
+ RETURNING syntax as modern versions.