Repository navigation
Version 2.2.0 has a negative impact on SQLAchemy dialect's parameter handling and results #806
Description
Problem
With version 2.2.0, released a few hours ago, we are observing a few errors with client code that uses the SQLAlchemy dialect, happening within its test suite and a few test cases in CTK.
Possibly, only a few adjustments are needed. Alternatively, we may want to roll back by pruning the release package from PyPI if the change or its impact are too serious, or not ready for GA yet.
Even after adjusting some test cases with crate/sqlalchemy-cratedb#266, doctests are failing with wrong results, see examples below.
Examples
SQLParseException[line 1:57: no viable alternative at input 'VALUES (%']
Code:
result.rowcount
Expected:
10
Got:
0
Expected:
'Algol'
Got:
'Earth'
/cc @bgunebakan, @florinutz
Activity
[-]SQLParseException[line 1:57: no viable alternative at input 'VALUES (%'][/-][+]Version 2.2.0 has a negative impact on SQLAchemy dialect's parameter handling and results[/+]amotl commentedon Jun 4, 2026
I've just yanked
crate-2.2.0from PyPI, because it showed anomalies on the SQLAlchemy dialect, as demonstrated above.bgunebakan commentedon Jun 16, 2026
Thank you for your quick action. Required fixes have merged, so I'm closing this issue. It will be fixed on new release.
amotl commentedon Jun 16, 2026
Thanks a stack for resolving the hiccup more sustainably. 💯
amotl commentedon Jun 18, 2026
Hi again. We've created a separate issue about our observations with v2.2.1. 🙏