[LucaCappelletti94]

Since version 16, PostgreSQL reads 0x1F, 0X1F, 0o17 and 0b101 as integers, with underscores allowed as in 0x_FF_FF (docs). PostgreSqlDialect turned 0x1F into Value::HexStringLiteral("1F"), the same value as the bit string X'1F', and split the other spellings into a zero followed by an alias, so SELECT 0o17 came back as SELECT 0 AS o17.

The new Dialect::supports_non_decimal_integer_literals, enabled for PostgreSQL, makes the tokenizer read these prefixes into a Number token that keeps the literal as written, so it round-trips. With the bigdecimal feature the value is stored as its decimal, the same way 10_000 already is. Other dialects, GenericDialect included, keep 0x as a hex string, as MySQL and SQL Server read it.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.52%. Comparing base (a9c0767) to head (81b1cfa).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2758      +/-   ##
==========================================
+ Coverage   82.48%   82.52%   +0.04%     
==========================================
  Files          42       42              
  Lines       35468    35533      +65     
  Branches    35468    35533      +65     
==========================================
+ Hits        29255    29323      +68     
+ Misses       2676     2675       -1     
+ Partials     3537     3535       -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.

[s5dsn-eqee]

LGTM!

[LucaCappelletti94]

Thanks @s5dsn-eqee for the review, I will be merging this now.

cc @alamb