Adjust version numbers for some changes, tags

Change-Id: I53263bd27a9012f1c41a2c491441c5fed79df673
(cherry picked from commit 8ecfecefe81f4fef6ed30ad46b7a36d76e3ea14b)

diff --git a/doc/build/changelog/unreleased_13/6007.rst b/doc/build/changelog/unreleased_13/6007.rst
index 5b06e18b6b005a75b23dadd2057a5288be3b1aaf..62c5af1d4c39940435b4b7c55c13f5fa45f1c15f 100644 (file)
--- a/doc/build/changelog/unreleased_13/6007.rst
+++ b/doc/build/changelog/unreleased_13/6007.rst
@@ -1,5 +1,5 @@
 .. change::
-    :tags: bug, sql, sqlite
+    :tags: bug, schema, sqlite
     :tickets: 6007
     :versions: 1.4.0
 

diff --git a/doc/build/changelog/unreleased_13/6023.rst b/doc/build/changelog/unreleased_13/6023.rst
index 2cfe885678d707af6d398b4cd7f7d0bf40d787fc..1c4b6ac8ceb0c7c0dfc271e7ff44ad52b1821e1b 100644 (file)
--- a/doc/build/changelog/unreleased_13/6023.rst
+++ b/doc/build/changelog/unreleased_13/6023.rst
@@ -1,6 +1,7 @@
 .. change::
     :tags: bug, types, postgresql
     :tickets: 6023
+    :versions: 1.4.3
 
     Adjusted the psycopg2 dialect to emit an explicit PostgreSQL-style cast for
     bound parameters that contain ARRAY elements. This allows the full range of

diff --git a/doc/build/changelog/unreleased_13/6071.rst b/doc/build/changelog/unreleased_13/6071.rst
index f9a04c98cd474e1c6f5159de00cbde9e92564eaa..44e8abfabab03ce51769616575e8b02b89f3cbb8 100644 (file)
--- a/doc/build/changelog/unreleased_13/6071.rst
+++ b/doc/build/changelog/unreleased_13/6071.rst
@@ -1,5 +1,12 @@
 .. change::
     :tags: bug, schema
     :tickets: 6071
+    :versions: 1.4.3
 
-    Allow dropping a schema with a sequence shared by more than one table.
+    Adjusted the logic that emits DROP statements for :class:`_schema.Sequence`
+    objects among the dropping of multiple tables, such that all
+    :class:`_schema.Sequence` objects are dropped after all tables, even if the
+    given :class:`_schema.Sequence` is related only to a :class:`_schema.Table`
+    object and not directly to the overall :class:`_schema.MetaData` object.
+    The use case supports the same :class:`_schema.Sequence` being associated
+    with more than one :class:`_schema.Table` at a time.