From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Fri, 18 Dec 2020 21:11:56 +0000 (-0500)
Subject: cherry-pick changelog from 1.3.22
X-Git-Tag: rel_1_4_0b2~89
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=eb305c8101710fd09331fe6df4b927dd4bc33a00;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

cherry-pick changelog from 1.3.22
---

diff --git a/doc/build/changelog/changelog_13.rst b/doc/build/changelog/changelog_13.rst
index c7bf4a0d62..bde93d6bc6 100644
--- a/doc/build/changelog/changelog_13.rst
+++ b/doc/build/changelog/changelog_13.rst
@@ -12,7 +12,23 @@
 
 .. changelog::
     :version: 1.3.22
-    :include_notes_from: unreleased_13
+    :released: December 18, 2020
+
+    .. change::
+        :tags: bug, oracle
+        :tickets: 5784
+        :versions: 1.4.0b2
+
+        Fixed regression which occured due to :ticket:`5755` which implemented
+        isolation level support for Oracle.   It has been reported that many Oracle
+        accounts don't actually have permission to query the ``v$transaction``
+        view so this feature has been altered to gracefully fallback when it fails
+        upon database connect, where the dialect will assume "READ COMMITTED" is
+        the default isolation level as was the case prior to SQLAlchemy 1.3.21.
+        However, explicit use of the :meth:`_engine.Connection.get_isolation_level`
+        method must now necessarily raise an exception, as Oracle databases with
+        this restriction explicitly disallow the user from reading the current
+        isolation level.
 
 .. changelog::
     :version: 1.3.21
diff --git a/doc/build/changelog/unreleased_13/5784.rst b/doc/build/changelog/unreleased_13/5784.rst
deleted file mode 100644
index 87ee080b5c..0000000000
--- a/doc/build/changelog/unreleased_13/5784.rst
+++ /dev/null
@@ -1,15 +0,0 @@
-.. change::
-    :tags: bug, oracle
-    :tickets: 5784
-    :versions: 1.4.0b2
-
-    Fixed regression which occured due to :ticket:`5755` which implemented
-    isolation level support for Oracle.   It has been reported that many Oracle
-    accounts don't actually have permission to query the ``v$transaction``
-    view so this feature has been altered to gracefully fallback when it fails
-    upon database connect, where the dialect will assume "READ COMMITTED" is
-    the default isolation level as was the case prior to SQLAlchemy 1.3.21.
-    However, explicit use of the :meth:`_engine.Connection.get_isolation_level`
-    method must now necessarily raise an exception, as Oracle databases with
-    this restriction explicitly disallow the user from reading the current
-    isolation level.
\ No newline at end of file