[LucaCappelletti94]

SQLite's operator table puts <, <=, > and >= one level above =, ==, <>, !=, IS, IN, LIKE and BETWEEN (https://www.sqlite.org/lang_expr.html#operators_and_parse_affecting_attributes). So a = b < c means a = (b < c): SQLite 3.51.1 evaluates SELECT 2 = 1 < 3 to 0, which only holds for 2 = (1 < 3). The SQLite dialect used a single level for all comparisons and parsed it as (a = b) < c.

SQLiteDialect now returns a separate precedence for <, <=, > and >=. Since the default table has no free value between = and the bitwise operators, the dialect overrides prec_value with the default levels shifted up by one above =. Other dialects are unchanged: PostgreSQL 16 and DuckDB 1.4.4 reject 2 = 1 < 3 outright, so there is no grouping to match there. Tests check the tree for each pairing, IN and BETWEEN against <, and that every other dialect still parses a = b < c as (a = b) < c.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.53%. Comparing base (424378c) to head (9f2dc0b).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2678      +/-   ##
==========================================
+ Coverage   81.52%   81.53%   +0.01%     
==========================================
  Files          42       42              
  Lines       34205    34224      +19     
  Branches    34205    34224      +19     
==========================================
+ Hits        27885    27904      +19     
  Misses       2770     2770              
  Partials     3550     3550              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.