"does not support reflection" -> "does not support nullable booleans"

Change-Id: Icf00f9250ffe45413369a6bb2c2910da42c017ee
(cherry picked from commit 051c2fde4c3b4bf7edcaa7578c0b1420986aaf0c)

diff --git a/README.dialects.rst b/README.dialects.rst
index f8c577ccb3839470024210a633ef434bd9d759a1..7335c0f0eaf467129c50d1fc11495599d61341c3 100644 (file)
--- a/README.dialects.rst
+++ b/README.dialects.rst
@@ -125,8 +125,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