[LucaCappelletti94]

In SQLite, comparison operators, IS, LIKE, NOTNULL and BETWEEN share one precedence level (https://www.sqlite.org/lang_expr.html#operators_and_parse_affecting_attributes), so the lower bound of a BETWEEN extends up to the AND: SQLite 3.51.1 runs 2 BETWEEN 1 > 0 AND 3, 2 BETWEEN NULL IS NULL AND 3, 2 BETWEEN 'a' LIKE 'a' AND 3 and a nested BETWEEN as the lower bound. The SQLite dialect stopped the lower bound at the BETWEEN precedence and failed with Expected: AND, found: >.

A new dialect method, between_low_bound_precedence, defaults to the BETWEEN precedence, and SQLiteDialect returns the AND precedence instead. The upper bound is unchanged, so operators after it still apply to the whole BETWEEN. Tests check the parsed lower bound and these forms in SQLite, and the unchanged error in the generic dialect.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.21%. Comparing base (a9b10d0) to head (a77caa9).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2664   +/-   ##
=======================================
  Coverage   82.20%   82.21%           
=======================================
  Files          42       42           
  Lines       35314    35320    +6     
  Branches    35314    35320    +6     
=======================================
+ Hits        29029    29037    +8     
  Misses       2716     2716           
+ Partials     3569     3567    -2     

☔ 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.