Re: [GENERAL] DROP [TEMP] TABLE syntax, as reason why not? - Mailing list pgsql-general

From Vincenzo Romano
Subject Re: [GENERAL] DROP [TEMP] TABLE syntax, as reason why not?
Date
Msg-id CAHjZ2x6HSNSFJjHmTz3zES5JuvyQRyGpbDB1q8MahWC=9G7-Xg@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] DROP [TEMP] TABLE syntax, as reason why not?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] DROP [TEMP] TABLE syntax, as reason why not?  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
2017-08-24 3:08 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>> I'm wondering if there is anything technical preventing someone from making:
>
>> DROP TEMP TABLE tablename;
>
> There is no great need for that because you can get the semantics you're
> asking for with "DROP TABLE pg_temp.tablename".
>
>                         regards, tom lane

This sounds like another syntax inconsistency/asymmetry.

ALTER TABLE pg_temp.tablename ... is OK.
ALTER TEMP TABLE tablename ... is NOT OK.

CREATE TEMP TABLE tablename ... is OK.
CREATE TABLE pg_temp.tablename ... is OK.

DROP TABLE pg_temp.tablename ... is OK.
DROP TEMP TABLE tablename ... is NOT OK.

Unless the standard explicitly forbids it, why not supporting both
syntaxes in all commands using the TABLE predicate?
Those are semantically equivalent. Aren't they?

--
Vincenzo Romano - NotOrAnd.IT
Information Technologies
--
NON QVIETIS MARIBVS NAVTA PERITVS


pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [GENERAL] 'value too long' and before insert/update trigger
Next
From: Benoit Lobréau
Date:
Subject: [GENERAL] Explain analyse and toasted data.