Repository navigation
New params handling does not play nice with compile() with literal_binds=True #13635
Description
The change made in #7066 improved the behaviour of params in most sql construct.
This apparently caused a regression when using compile_kwargs={"literal_binds": True}
import sqlalchemy as sa
t = sa.Table(
"t",
sa.MetaData(),
sa.Column("id", sa.Integer, primary_key=True),
sa.Column("name", sa.String()),
)
s = sa.select(t).where(t.c.id == sa.bindparam("id"))
s2 = s.params(id=1)
e = sa.create_engine("sqlite:///:memory:")
t.metadata.create_all(e)
e.echo = True
with e.connect() as conn:
result = conn.execute(s2).all()
c = s2.compile(dialect=e.dialect)
print(c.string, c.params)
c2 = s2.compile(dialect=e.dialect, compile_kwargs={"literal_binds": True})
print(c2.string, c2.params)this prints
2026-10-02 16:17:52,112 INFO sqlalchemy.engine.Engine BEGIN (implicit)
2026-10-02 16:17:52,112 INFO sqlalchemy.engine.Engine SELECT t.id, t.name
FROM t
WHERE t.id = ?
2026-10-02 16:17:52,112 INFO sqlalchemy.engine.Engine [generated in 0.00095s] (1,)
2026-10-02 16:17:52,113 INFO sqlalchemy.engine.Engine ROLLBACK
SELECT t.id, t.name
FROM t
WHERE t.id = ? {'id': 1}
path/to/file.py:21: SAWarning: Bound parameter 'id' rendering literal NULL in a SQL expression; comparisons to NULL should not use operators outside of 'is' or 'is not' (this warning may be suppressed after 10 occurrences)
c2 = s2.compile(dialect=e.dialect, compile_kwargs={"literal_binds": True})
SELECT t.id, t.name
FROM t
WHERE t.id = NULL {}
the param is lost when using literal binds
Activity
sqla-tester commentedon Oct 2, 2026
Mike Bayer has proposed a fix for this issue in the main branch:
render statement params with literal_binds https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/7023
render statement params with literal_binds
render statement params with literal_binds