changelog updates

Change-Id: I6e1bcdab140eb91926520984e6fc2c288f1dade1

diff --git a/docs/build/unreleased/1004.rst b/docs/build/unreleased/1004.rst
index b6a6908a41ea14b2c0164ba483c11d17d2398bf4..d629306b628be65879e7f5ff65fa2897896fc24c 100644 (file)
--- a/docs/build/unreleased/1004.rst
+++ b/docs/build/unreleased/1004.rst
@@ -5,5 +5,5 @@
     Fixed issue where using :meth:`.Operations.create_table` in conjunction
     with a :class:`.CheckConstraint` that referred to table-bound
     :class:`.Column` objects rather than string expressions would be added to
-    the parent table twice, resulting in an incorrect DDL sequence. Pull
-    request courtesy Nicolas CANIART.
+    the parent table potentially multiple times, resulting in an incorrect DDL
+    sequence. Pull request courtesy Nicolas CANIART.

diff --git a/docs/build/unreleased/977.rst b/docs/build/unreleased/977.rst
index e95e4b304380b10351fb2ef12c154592dc5b88c6..91fb76ac109902d9b351ac9ce96ef1a542bf5908 100644 (file)
--- a/docs/build/unreleased/977.rst
+++ b/docs/build/unreleased/977.rst
@@ -2,10 +2,12 @@
     :tags: bug, mssql
     :tickets: 977
 
-    Fixed bug where an alter_column() operation would change a "NOT NULL"
-    column to "NULL" by emitting an ALTER COLUMN statement that did not specify
-    "NOT NULL". (In the absence of "NOT NULL" T-SQL was implicitly assuming
-    "NULL"). An alter_column() operation that specifies `type_=` should also
-    specify either `nullable=` or `existing_nullable=` to inform Alembic as to
-    whether the emitted DDL should include "NULL" or "NOT NULL"; a warning is
-    now emitted if this is missing under this scenario.
+    Fixed bug where an :meth:`.Operations.alter_column` operation would change
+    a "NOT NULL" column to "NULL" by emitting an ALTER COLUMN statement that
+    did not specify "NOT NULL". (In the absence of "NOT NULL" T-SQL was
+    implicitly assuming "NULL"). An :meth:`.Operations.alter_column` operation
+    that specifies :paramref:`.Operations.alter_column.type` should also
+    specify include either :paramref:`.Operations.alter_column.nullable` or
+    :paramref:`.Operations.alter_column.existing_nullable` to inform Alembic as
+    to whether the emitted DDL should include "NULL" or "NOT NULL"; a warning
+    is now emitted if this is missing under this scenario.

diff --git a/docs/build/unreleased/986.rst b/docs/build/unreleased/986.rst
index 6834d9d1da7974b229f6d3ab8e3d9157de5e65e8..a1b48cc5b88488e0e1b3ec023ec295a1b81a3d0e 100644 (file)
--- a/docs/build/unreleased/986.rst
+++ b/docs/build/unreleased/986.rst
@@ -2,6 +2,8 @@
     :tags: bug, environment
     :tickets: 986
 
-    The ``fileConfig()`` line in the ``env.py`` templates is now conditional on
-    ``Config.config_file_name`` not being None.
+    The ``logging.fileConfig()`` line in ``env.py`` templates, which is used
+    to setup Python logging for the migration run, is now conditional on
+    :attr:`.Config.config_file_name` not being ``None``.  Otherwise, the line
+    is skipped as there is no default logging configuration present.