From: Mike Bayer Date: Tue, 17 Dec 2019 14:57:30 +0000 (-0500) Subject: "does not support reflection" -> "does not support nullable booleans" X-Git-Tag: rel_1_3_13~32 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d549c241df14d0feac540a361a40e707ed66066b;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git "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 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