I had a test schema containing one table.
olly=# drop schema testing;
NOTICE: table testing.testa depends on schema testing
ERROR: Cannot drop schema testing because other objects depend on it
Use DROP ... CASCADE to drop the dependent objects too
This seems a little over-restrictive to me. There is no dependency
outside the schema, so shouldn't that have worked? I should have
thought CASCADE would be implicit for objects inside the schema to be
dropped.
--
Oliver Elphick [EMAIL PROTECTED]
Isle of Wight, UK
http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"For the Lord himself shall descend from heaven with a
shout, with the voice of the archangel, and with the
trump of God; and the dead in Christ shall rise first;
Then we which are alive and remain shall be caught
up together with them in the clouds, to meet the Lord
in the air; and so shall we ever be with the Lord."
I Thessalonians 4:16,17
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
