Search Postgresql Archives

Re: DROP [TEMP] TABLE syntax, as reason why not?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





2017-08-24 9:11 GMT+02:00 Vincenzo Romano <vincenzo.romano@xxxxxxxxxxx>:
2017-08-24 3:08 GMT+02:00 Tom Lane <tgl@xxxxxxxxxxxxx>:
> "David G. Johnston" <david.g.johnston@xxxxxxxxx> 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?

It can be issue when somebody will do port from PostgreSQL to any other databases. There should be stronger reason for introduction possible NON ANSI SQL feature than syntactic sugar.

Regards

Pavel

 

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


--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux