Drop Cascade of Domains

[elein]

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?

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.

Is there a previous rule on this issue?

--elein

================================================== ==========
el***@varlena.com Varlena, LLC www.varlena.com

PostgreSQL Consulting, Support & Training

PostgreSQL General Bits http://www.varlena.com/GeneralBits/
================================================== ===========
"Free your mind the rest will follow" -- En Vogue

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Peter Eisentraut]

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 that
tables with zero columns are valid, and the behavior of all commands and
side effects has been aligned with that.

--
Peter Eisentraut pe*****@gmx.net
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Tom Lane]

elein <el***@varlena.com> 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.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings