]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commitdiff
"does not support reflection" -> "does not support nullable booleans"
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 17 Dec 2019 14:57:30 +0000 (09:57 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 17 Dec 2019 14:57:30 +0000 (09:57 -0500)
Change-Id: Icf00f9250ffe45413369a6bb2c2910da42c017ee

README.dialects.rst

index 6c4df1019b552647c5fe5eebe6af8fc0cb313ff9..b300128bb224ea3338c92ba128bad93eab1b62fb 100644 (file)
@@ -123,8 +123,8 @@ Key aspects of this file layout include:
   For a third-party dialect, the custom ``Requirements`` class can
   usually specify a simple yes/no answer for a particular system. For
   example, a requirements file that specifies a database that supports
-  the RETURNING construct but does not support reflection of tables
-  might look like this::
+  the RETURNING construct but does not support nullable boolean
+  columns might look like this::
 
       # sqlalchemy_access/requirements.py