Pin non_native_boolean_check_constraint and update_returning_multifrom

The dqlite dialect already pins supports_native_boolean,
supports_native_decimal, the insert/update/delete RETURNING flags,
supports_multivalues_insert, supported_isolation_levels, and
supports_statement_cache against upstream drift. Two adjacent flags
inherit silently from SQLiteDialect:

- non_native_boolean_check_constraint. SQLAlchemy's Boolean type
  compiler gates this behind not supports_native_boolean, so it is
  functionally inert today. Pin False so the pair stays coherent if
  a future SQLAlchemy release decouples the two.

- update_returning_multifrom. Available on SQLite >= 3.33, which
  dqlite is. Pin True alongside the existing RETURNING trio so the
  same upstream-drift argument applies.

Both pins use the local-declaration pattern established by the
RETURNING pins (asserting the flag lives in DqliteDialect.__dict__,
not just inherited), so silent re-inheritance would fail the pin
tests.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: antoineleclair

src/sqlalchemydqlite/base.py

@@ -81,6 +81,13 @@ class DqliteDialect(SQLiteDialect):
     # to emit a ``CHECK (col IN (0, 1))`` constraint — the wire
     # contract enforces the 0/1 invariant.
     supports_native_boolean = True
+    # SQLAlchemy's Boolean type compiler gates
+    # ``non_native_boolean_check_constraint`` behind
+    # ``supports_native_boolean``, so the flag is functionally inert
+    # for us today. Pin False anyway to document intent and to keep
+    # the pin in lockstep with ``supports_native_boolean`` if a future
+    # SQLAlchemy release decouples the two.
+    non_native_boolean_check_constraint = False
 
     # dqlite runs every statement through Raft consensus; there is no
     # exposed way to weaken isolation. Declaring this explicitly lets
@@ -102,9 +109,11 @@ class DqliteDialect(SQLiteDialect):
     # SQLiteDialect's RETURNING detection (e.g. version-gated discovery)
     # can't silently change dqlite behaviour. All three of SQLAlchemy 2.x's
     # tripartite RETURNING flags default to True on the parent class today.
+    # Same reasoning applies to the multi-FROM RETURNING variant.
     insert_returning = True
     update_returning = True
     delete_returning = True
+    update_returning_multifrom = True
 
     # SQLite >= 3.7.11 supports multi-row INSERT VALUES, which SQLAlchemy's
     # insertmanyvalues optimisation depends on. Pin the flag so bulk-insert

tests/test_dialect.py

@@ -70,6 +70,21 @@ def test_supports_multivalues_insert_pinned_locally(self) -> None:
         assert DqliteDialect.supports_multivalues_insert is True
         assert "supports_multivalues_insert" in DqliteDialect.__dict__
 
+    def test_non_native_boolean_check_constraint_pinned_locally(self) -> None:
+        # dqlite declares supports_native_boolean = True, so the CHECK
+        # constraint is semantically unnecessary. Pin to False so a
+        # future SQLAlchemy release cannot silently flip the inherited
+        # value while native boolean support is already claimed.
+        assert DqliteDialect.non_native_boolean_check_constraint is False
+        assert "non_native_boolean_check_constraint" in DqliteDialect.__dict__
+
+    def test_update_returning_multifrom_pinned_locally(self) -> None:
+        # dqlite's SQLite is >= 3.35, which supports multi-FROM RETURNING.
+        # Pin locally for the same upstream-drift reason as the three
+        # RETURNING flags above.
+        assert DqliteDialect.update_returning_multifrom is True
+        assert "update_returning_multifrom" in DqliteDialect.__dict__
+
     def test_dialect_description(self) -> None:
         # Pin the derived dialect_description so SQLAlchemy upgrades cannot
         # silently change the rendered identity in ORM error messages.