From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Fri, 16 Feb 2018 20:55:11 +0000 (-0500)
Subject: - 0.9.8
X-Git-Tag: rel_0_9_8
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a32d9209313cb87415353dfca8e10683c4b85d24;p=thirdparty%2Fsqlalchemy%2Falembic.git

- 0.9.8
---

diff --git a/docs/build/changelog.rst b/docs/build/changelog.rst
index c57e71f7..0a9b675f 100644
--- a/docs/build/changelog.rst
+++ b/docs/build/changelog.rst
@@ -5,7 +5,60 @@ Changelog
 
 .. changelog::
     :version: 0.9.8
-    :include_notes_from: unreleased
+    :released: February 16, 2018
+
+    .. change::
+        :tags: bug, runtime
+        :tickets: 482
+
+        Fixed bug where the :meth:`.Script.as_revision_number` method
+        did not accommodate for the 'heads' identifier, which in turn
+        caused the :meth:`.EnvironmentContext.get_head_revisions`
+        and :meth:`.EnvironmentContext.get_revision_argument` methods
+        to be not usable when multiple heads were present.
+        The :meth:.`EnvironmentContext.get_head_revisions` method returns
+        a tuple in all cases as documented.
+
+
+
+    .. change::
+        :tags: bug, postgresql, autogenerate
+        :tickets: 478
+
+        Fixed bug where autogenerate of :class:`.ExcludeConstraint`
+        would render a raw quoted name for a Column that has case-sensitive
+        characters, which when invoked as an inline member of the Table
+        would produce a stack trace that the quoted name is not found.
+        An incoming Column object is now rendered as ``sa.column('name')``.
+
+    .. change::
+        :tags: bug, autogenerate
+        :tickets: 468
+
+        Fixed bug where the indexes would not be included in a
+        migration that was dropping the owning table.   The fix
+        now will also emit DROP INDEX for the indexes ahead of time,
+        but more importantly will include CREATE INDEX in the
+        downgrade migration.
+
+    .. change::
+        :tags: bug, postgresql
+        :tickets: 480
+
+        Fixed the autogenerate of the module prefix
+        when rendering the text_type parameter of
+        postgresql.HSTORE, in much the same way that
+        we do for ARRAY's type and JSON's text_type.
+
+    .. change::
+        :tags: bug, mysql
+        :tickets: 479
+
+        Added support for DROP CONSTRAINT to the MySQL Alembic
+        dialect to support MariaDB 10.2 which now has real
+        CHECK constraints.  Note this change does **not**
+        add autogenerate support, only support for op.drop_constraint()
+        to work.
 
 .. changelog::
     :version: 0.9.7
diff --git a/docs/build/unreleased/468.rst b/docs/build/unreleased/468.rst
deleted file mode 100644
index 3abc974e..00000000
--- a/docs/build/unreleased/468.rst
+++ /dev/null
@@ -1,9 +0,0 @@
-.. change::
-    :tags: bug, autogenerate
-    :tickets: 468
-
-    Fixed bug where the indexes would not be included in a
-    migration that was dropping the owning table.   The fix
-    now will also emit DROP INDEX for the indexes ahead of time,
-    but more importantly will include CREATE INDEX in the
-    downgrade migration.
diff --git a/docs/build/unreleased/478.rst b/docs/build/unreleased/478.rst
deleted file mode 100644
index 8c479b0b..00000000
--- a/docs/build/unreleased/478.rst
+++ /dev/null
@@ -1,9 +0,0 @@
-.. change::
-    :tags: bug, postgresql, autogenerate
-    :tickets: 478
-
-    Fixed bug where autogenerate of :class:`.ExcludeConstraint`
-    would render a raw quoted name for a Column that has case-sensitive
-    characters, which when invoked as an inline member of the Table
-    would produce a stack trace that the quoted name is not found.
-    An incoming Column object is now rendered as ``sa.column('name')``.
diff --git a/docs/build/unreleased/479.rst b/docs/build/unreleased/479.rst
deleted file mode 100644
index feebb891..00000000
--- a/docs/build/unreleased/479.rst
+++ /dev/null
@@ -1,9 +0,0 @@
-.. change::
-    :tags: bug, mysql
-    :tickets: 479
-
-    Added support for DROP CONSTRAINT to the MySQL Alembic
-    dialect to support MariaDB 10.2 which now has real
-    CHECK constraints.  Note this change does **not**
-    add autogenerate support, only support for op.drop_constraint()
-    to work.
diff --git a/docs/build/unreleased/480.rst b/docs/build/unreleased/480.rst
deleted file mode 100644
index f753e7fe..00000000
--- a/docs/build/unreleased/480.rst
+++ /dev/null
@@ -1,8 +0,0 @@
-.. change::
-    :tags: bug, postgresql
-    :tickets: 480
-
-    Fixed the autogenerate of the module prefix
-    when rendering the text_type parameter of
-    postgresql.HSTORE, in much the same way that
-    we do for ARRAY's type and JSON's text_type.
diff --git a/docs/build/unreleased/482.rst b/docs/build/unreleased/482.rst
deleted file mode 100644
index 67eb1a83..00000000
--- a/docs/build/unreleased/482.rst
+++ /dev/null
@@ -1,13 +0,0 @@
-.. change::
-    :tags: bug, runtime
-    :tickets: 482
-
-    Fixed bug where the :meth:`.Script.as_revision_number` method
-    did not accommodate for the 'heads' identifier, which in turn
-    caused the :meth:`.EnvironmentContext.get_head_revisions`
-    and :meth:`.EnvironmentContext.get_revision_argument` methods
-    to be not usable when multiple heads were present.
-    The :meth:.`EnvironmentContext.get_head_revisions` method returns
-    a tuple in all cases as documented.
-
-