> With DROP CASCADE, he can get rid of > everything within > the schema at a blow, so this is really pretty close to the same > functionality. but beware of cross-schema dependencies! e.g., a DROP SCHEMA CASCADE of schema X containg a table that has a column defined using a domain from schema Y will result either in that object (the domain) being dropped from schema Y (if user has privileges on Y) or in a failure of the DROP (if not)...
