[moshap-firebolt]

Databricks and Hive both write a BIGINT literal with an L suffix (Databricks, Hive), but both dialects read it as an identifier:

SELECT 1L
-- Databricks, Hive: Identifier(Ident { value: "1L", .. })

Their numeric-prefix rule, which allows table names like 59901_user_login, runs before the tokenizer looks for the suffix. Hive's long_numerics test passed only because the identifier 1L prints back unchanged.

This adds Dialect::supports_long_suffix_before_numeric_prefix, enabled for both: an L that ends the number makes it a long, and 1La is still an identifier. MySQL, which has a numeric prefix but no long literal, keeps reading 1L as an identifier. As elsewhere in the tokenizer, only an uppercase L is a suffix. Databricks DIV, CREATE TABLE ... USING and LONG are left to #2425.

Tests in sqlparser_common.rs cover dialects with and without the method; they fail without the change.

This PR was prepared with AI assistance (Claude).

Dialects: Databricks, Hive

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.62%. Comparing base (c6cec56) to head (d9a8008).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2771      +/-   ##
==========================================
+ Coverage   82.60%   82.62%   +0.01%     
==========================================
  Files          42       42              
  Lines       35607    35627      +20     
  Branches    35607    35627      +20     
==========================================
+ Hits        29414    29436      +22     
  Misses       2659     2659              
+ Partials     3534     3532       -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.