SQL Server supports what SQLAlchemy calls "native boolean"
with its BIT type, as this type only accepts 0 or 1 and the
DBAPIs return its value as True/False. So the SQL Server
dialects now enable "native boolean" support, in that a
CHECK constraint is not generated for a :class:`.Boolean`
datatype. The only difference vs. other native boolean
is that there are no "true" / "false" constants so "1" and
"0" are still rendered here.
Tests are implicit in the existing suites.
Change-Id: I75bbcd549884099fb1a177e68667bf880c40fa7c
Fixes: #4061
--- /dev/null
+.. change::
+ :tags: bug, mssql
+ :tickets: 4061
+
+ SQL Server supports what SQLAlchemy calls "native boolean"
+ with its BIT type, as this type only accepts 0 or 1 and the
+ DBAPIs return its value as True/False. So the SQL Server
+ dialects now enable "native boolean" support, in that a
+ CHECK constraint is not generated for a :class:`.Boolean`
+ datatype. The only difference vs. other native boolean
+ is that there are no "true" / "false" constants so "1" and
+ "0" are still rendered here.
+
ischema_names = ischema_names
- supports_native_boolean = False
+ supports_native_boolean = True
supports_unicode_binds = True
postfetch_lastrowid = True
return bool
def literal_processor(self, dialect):
- if dialect.supports_native_boolean:
- def process(value):
- return "true" if value else "false"
- else:
- def process(value):
- return str(1 if value else 0)
+ compiler = dialect.statement_compiler(dialect, None)
+ true = compiler.visit_true(None)
+ false = compiler.visit_false(None)
+
+ def process(value):
+ return true if value else false
return process
def bind_processor(self, dialect):