[LucaCappelletti94]

DROP TABLE on a partitioned table was refused while it had partitions, because every table below the dropped one was treated like an INHERITS child that only CASCADE may take along. PostgreSQL drops a partitioned table's partitions with it on its own, nested and attached ones included, and keeps requiring CASCADE only for INHERITS children. The drop now follows that, and dropping a partition leaves its root standing.

Since partitions now leave with their root, a view reading one of them or a foreign key pointing at one from a table that stays holds the drop back the same way it does for the named table, and CASCADE removes the view or cuts the key. The cascaded INHERITS drop gains the same view removal, which used to leave views on the children behind. Every name in the statement resolves before anything is dropped, as in PostgreSQL, so DROP TABLE p, c drops both and an absent name is reported before anything changes.

This stacks on #172 because main cannot build against the current sqlparser until that one merges.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!