| From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Kevin Grittner <kgrittn(at)postgresql(dot)org>, "pgsql-committers(at)postgresql(dot)org" <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Add infrastructure to support EphemeralNamedRelation references. |
| Date: | 2017-04-08 01:26:32 |
| Message-ID: | CAHE3wgg5D7O=vFdNU4FV0BgDiQb0c+tUVW6hFwJ+uqemz6F+BA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
2017-04-07 13:06 GMT-03:00 Kevin Grittner <kgrittn(at)gmail(dot)com>:
> ERROR: cannot drop table t1 column t1id because other objects depend on it
> DETAIL: view v1 depends on table t1 column t1id
> HINT: Use DROP ... CASCADE to drop the dependent objects too.
>
> Is that comment wrong?
>
Sort of. If you consider ALTER TABLE ... DROP COLUMN ... CASCADE, it is not
that wrong. However, if you want to be strict, there should be a check to
identify a table column and then hint a specific message (ALTER instead of
DROP).
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2017-04-08 01:51:04 | Re: pgsql: Add infrastructure to support EphemeralNamedRelation references. |
| Previous Message | Tom Lane | 2017-04-08 01:23:51 | Re: pgsql: Use SASLprep to normalize passwords for SCRAM authentication. |