[LucaCappelletti94]

In SQLite ~ is the unary bitwise NOT operator (https://www.sqlite.org/lang_expr.html#operators_and_parse_affecting_attributes), so SELECT ~~5 applies it twice and returns 5. The tokenizer always read ~~ as PostgreSQL's LIKE match operator, so SELECT ~~a FROM t failed to parse with the SQLite dialect (Expected: an expression, found: ~~).

A new dialect method, supports_tilde_like_match_operator, defaults to true so every other dialect keeps today's tokenization, and SQLiteDialect returns false, which makes ~~ and ~~~ tokenize as separate ~ tokens. The SQLite test covers both, and the dialects that keep the operator are tested to still parse a ~~ b and still reject a leading ~~.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.33%. Comparing base (3330dc9) to head (5b33d0e).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2659      +/-   ##
==========================================
+ Coverage   81.31%   81.33%   +0.02%     
==========================================
  Files          42       42              
  Lines       33977    34010      +33     
  Branches    33977    34010      +33     
==========================================
+ Hits        27628    27662      +34     
+ Misses       2785     2784       -1     
  Partials     3564     3564              

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