From d549c241df14d0feac540a361a40e707ed66066b Mon Sep 17 00:00:00 2001
From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Tue, 17 Dec 2019 09:57:30 -0500
Subject: [PATCH] "does not support reflection" -> "does not support nullable
 booleans"

Change-Id: Icf00f9250ffe45413369a6bb2c2910da42c017ee
(cherry picked from commit 051c2fde4c3b4bf7edcaa7578c0b1420986aaf0c)
---
 README.dialects.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.dialects.rst b/README.dialects.rst
index f8c577ccb3..7335c0f0ea 100644
--- 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
 
-- 
2.47.2