From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Nina Marlow <postgresql(dot)2020(at)t-net(dot)ruhr> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16492: DROP VIEW IF EXISTS error |
Date: | 2020-06-14 10:51:58 |
Message-ID: | CAFj8pRDyZb9Rt6Dst_9uf+A2r0e2iQRkoys7+JeR9E-voPDNnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
so 13. 6. 2020 v 13:41 odesílatel Nina Marlow <postgresql(dot)2020(at)t-net(dot)ruhr>
napsal:
> > DROP TABLE IF EXISTS and DROP TABLE are consistent now. The message is
> > ""xxx" is not a view", it is not ""xxx" doesn't exist".
>
> Yes, but according to the documentation, there shouldn't be an error at
> all ("Do not throw an error if the *view* does not exist."). It doesn't
> say, "do not throw an error if the *object* does not exist", but "if the
> *view* does not exist". This is very clear to me.
>
> So it's either a documentation error or a code error. It cannot be none.
>
I prefer to fix the documentation. Current behavior looks a little bit
more practical and a little bit more safe, although I can understand very
well the different opinion.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-06-14 16:19:36 | Re: BUG #16492: DROP VIEW IF EXISTS error |
Previous Message | Peter Geoghegan | 2020-06-13 18:37:08 | Re: Potential G2-item cycles under serializable isolation |