[LucaCappelletti94]

Follow-up to #2664, which this PR is stacked on.

PostgreSQL, DuckDB and Spark accept one comparison in the lower bound of a BETWEEN, as in x BETWEEN 1 > 0 AND y, but reject IS, LIKE or a nested BETWEEN there. PostgreSQL 16 and DuckDB 1.4.4 run SELECT true BETWEEN 1 > 0 AND true, true BETWEEN 1 <> 2 AND true and true BETWEEN 1 + 1 >= 2 AND true, and both reject true BETWEEN 1 = 1 = true AND true with a syntax error. Spark's grammar parses the bound as a valueExpression, which includes comparison (https://github.com/apache/spark/blob/master/sql/api/src/main/antlr4/org/apache/spark/sql/catalyst/parser/SqlBaseParser.g4). These dialects stopped the bound before the comparison and failed with Expected: AND, found: >.

A single precedence threshold cannot express this, because PostgreSQL ranks LIKE and BETWEEN above comparisons. A new dialect method, supports_comparison_in_between_low_bound, lets the parser read one comparison after the bound, with its right side parsed at BETWEEN precedence. It is enabled for PostgreSQL, DuckDB, Spark, Databricks and the generic dialect. Tests check the parsed bound and the rejected forms in those dialects, and the unchanged error everywhere else.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.22%. Comparing base (fcd2328) to head (5e0d022).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2665      +/-   ##
==========================================
+ Coverage   82.21%   82.22%   +0.01%     
==========================================
  Files          42       42              
  Lines       35320    35343      +23     
  Branches    35320    35343      +23     
==========================================
+ Hits        29037    29060      +23     
  Misses       2716     2716              
  Partials     3567     3567              

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

[alamb]

can we instead update the test to show what happens with this statement rather than deleting it now? I assume it parses correctly?

[LucaCappelletti94]

The case is already covered in parse_comparison_in_between_low_bound, that's why I dropped it.