From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Nina Marlow <postgresql(dot)2020(at)t-net(dot)ruhr>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16492: DROP VIEW IF EXISTS error |
Date: | 2020-06-14 16:19:36 |
Message-ID: | CAKFQuwYkzKP17j1RS2ASL7oMnnbZW8qBb=kR3-e1Ug9QpnBvxw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sunday, June 14, 2020, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>
> 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.
>
>
How is the proposed behavior more risky? And no, the current behavior does
not have any uniquely practical use. Its only benefit is that it is how
things have worked forever and that is only because its flaws are rarely
encountered in practice.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-06-14 17:12:15 | Re: BUG #16492: DROP VIEW IF EXISTS error |
Previous Message | Pavel Stehule | 2020-06-14 10:51:58 | Re: BUG #16492: DROP VIEW IF EXISTS error |