[LucaCappelletti94]

In CREATE TABLE ... PARTITION OF, a column entry is column_name [ WITH OPTIONS ] [ column_constraint ... ] and carries no data type (https://www.postgresql.org/docs/current/sql-createtable.html). The parser always read a type there, so (id NOT NULL) became a column of type NOT with a NULL option, and (id) or (id DEFAULT 0) failed to parse.

In the PARTITION OF form, column entries now parse with DataType::Unspecified, the shape SQLite's untyped columns already use. WITH OPTIONS is a noise word that PostgreSQL's own parse tree also discards, so it is accepted and dropped like [ COLUMN ] in ALTER TABLE. A data type in this position is now rejected, as PostgreSQL rejects it.

Thanks to @s5dsn-eqee for spotting this one.

Closes #2762.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 96.66667% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 82.62%. Comparing base (1e0bc45) to head (947917f).

Files with missing lines	Patch %	Lines
src/parser/mod.rs	96.66%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2766      +/-   ##
==========================================
+ Coverage   82.61%   82.62%   +0.01%     
==========================================
  Files          42       42              
  Lines       35614    35633      +19     
  Branches    35614    35633      +19     
==========================================
+ Hits        29421    29442      +21     
  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.

[s5dsn-eqee]

LGTM!