On 29 September 2012 18:08, Andreas wrote:
> Hi
> I encountered something that puzzled me a bit.
> Is it expected that DROP table CASCADE drops this table and just the
> foreign key constraints but not the refering tables?
>
> PG 9.2.1 on WinXP
>
>
>
Hi Andreas,
yes, it is expected, at least acco
elein <[EMAIL PROTECTED]> writes:
> I have a table which contains three
> columns of domain X.
> If I drop the domain X with cascade,
> the table remains with no columns.
> Is this the proper behaviour?
Yes, we agreed some time ago that that is the best thing to do.
regard
elein writes:
> It seems to me that any action which
> results in an invalid object should be
> forbidden. On the other hand, with
> alter table working well, I am loathe
> to argue a table with no columns is
> an invalid argument.
While not allowed according to the SQL standard, we have decided
