Fixed bug in SQL Server dialect with new "max_identifier_length" feature
where the mssql dialect already featured this flag, and the implementation
did not accommodate for the new initialization hook correctly.
Fixes: #4857
Change-Id: I96a9c6ca9549d8f6fb167c0333f684e8d922a3bf
--- /dev/null
+.. change::
+ :tags: bug, mssql
+ :tickets: 4857
+
+ Fixed bug in SQL Server dialect with new "max_identifier_length" feature
+ where the mssql dialect already featured this flag, and the implementation
+ did not accommodate for the new initialization hook correctly.
+
self,
query_timeout=None,
use_scope_identity=True,
- max_identifier_length=None,
schema_name="dbo",
isolation_level=None,
deprecate_large_types=None,
self.schema_name = schema_name
self.use_scope_identity = use_scope_identity
- self.max_identifier_length = (
- int(max_identifier_length or 0) or self.max_identifier_length
- )
self.deprecate_large_types = deprecate_large_types
self.legacy_schema_aliasing = legacy_schema_aliasing
class MaxIdentTest(fixtures.TestBase, AssertsCompiledSQL):
__dialect__ = "DefaultDialect"
+ __backend__ = True
table1 = table(
"some_large_named_table",