From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Sun, 29 Oct 2023 20:15:52 +0000 (-0400)
Subject: changelog updates
X-Git-Tag: rel_2_0_23~6
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6a27c2dfa60820b7c3b50c40478de8e5bef32909;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

changelog updates

Change-Id: I6b362500f1fab118920d61f8b6247521756922ff
---

diff --git a/doc/build/changelog/unreleased_20/10056.rst b/doc/build/changelog/unreleased_20/10056.rst
index d801e98eac..fb16b6ef8a 100644
--- a/doc/build/changelog/unreleased_20/10056.rst
+++ b/doc/build/changelog/unreleased_20/10056.rst
@@ -1,8 +1,10 @@
 .. change::
-    :tags: bug, sql
+    :tags: bug, mariadb
     :tickets: 10056
 
-    mariaDB does not support setting NOT NULL for generated column
-    ref: https://mariadb.com/kb/en/generated-columns/#statement-support
-    added a check in `get_column_specification` for mariadb, checking
-    if user has not specified nullable set it as True for computed column.
+    Adjusted the MySQL / MariaDB dialects to default a generated column to NULL
+    when using MariaDB, if :paramref:`_schema.Column.nullable` was not
+    specified with an explicit ``True`` or ``False`` value, as MariaDB does not
+    support the "NOT NULL" phrase with a generated column.  Pull request
+    courtesy Indivar.
+
diff --git a/doc/build/changelog/unreleased_20/10532.rst b/doc/build/changelog/unreleased_20/10532.rst
index ba379cf768..c0308a454d 100644
--- a/doc/build/changelog/unreleased_20/10532.rst
+++ b/doc/build/changelog/unreleased_20/10532.rst
@@ -5,7 +5,7 @@
     Fixed SQL handling for "insertmanyvalues" when using the
     :class:`.postgresql.BIT` datatype with the asyncpg backend.  The
     :class:`.postgresql.BIT` on asyncpg apparently requires the use of an
-    asyncpg-specific `BitString` type which is currently exposed when using
+    asyncpg-specific ``BitString`` type which is currently exposed when using
     this DBAPI, making it incompatible with other PostgreSQL DBAPIs that all
     work with plain bitstrings here.  A future fix in version 2.1 will
     normalize this datatype across all PG backends.   Pull request courtesy