In DROP TABLE statement, make table order irrelevant
Current behavior is described in the docs: "If both the referencing table and the table that holds the primary key are being dropped in the same DROP TABLE statement, the referencing table must be listed first."
It would be great to not worry about order.
It should be possible to list the tables in any order as long as any foreign key referencing tables that are being dropped, are also being dropped in the same statement.
12
votes
