Re: Remove all tables for user with one SQl statement?

On 19.12.2005 13:19 Robert Klemme wrote:
>>A "DROP TABLE xyz CASCADE CONSTRAINTS" will remove all constraints on
>>the table as well, including foreign keys.
>>
>>So the order shouldn't actually matter in that case, shouldn't it?

> 
> 
> And what do you do if a table X referencing table A you're about to delete
> references it?

But isn't "CASCADE CONSTRAINTS" intended to handle that:

The following script works without problems:

create table a (a_id integer primary key); create table x
(
  x_id integer primary key,
  fk_id integer references a(a_id)
);

insert into a values (1);
insert into x values (2,1);

commit;

drop table x cascade constraints;

I can also drop table a at the end (without dropping table x).

Even if I create another table referencing a, I can drop table a at any time without dropping any table referencing it.

So in which situation would a DROP using CASCADE CONSTRAINTS fail?

Thomas

-- 
It's not a RootKit - it's a Sony