Re: [GENERAL] Surprising syntax error

From: "Robert Haas" <robertmhaas(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, "Marc Munro" <marc(at)bloodnok(dot)com>
Subject: Re: [GENERAL] Surprising syntax error
Date: 2008-08-23 19:14:22
Message-ID: 603c8f070808231214p6a85b37cpfe4dcb4a2ae0deb8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

>> While we don't _need_ it, it would make our system more consistent; we
>> have made similar changes for views in other areas.
>
> I'm not sure it'd make the system more consistent. Because the SQL
> standard says you use GRANT ON TABLE for a view. we'd have to always
> ensure that we accepted that; whereas in at least some other places
> we are trying to be picky about TABLE/VIEW/SEQUENCE actually matching
> the object type.
>
> Given the spec precedent, I'm inclined to leave it alone. It's not like
> there aren't plenty of other SQL quirks that surprise novices.

I fail to understand why it's advantageous to artificially create
surprising behavior. There are cases where PostgreSQL now accepts
either ALTER VIEW or ALTER TABLE where it previously accepted only the
latter, so the situation is hardly without precedent. I find it
exceedingly unlikely that anyone is relying on GRANT ON VIEW to NOT
work.

...Robert

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2008-08-23 19:49:44 Re: [GENERAL] Surprising syntax error
Previous Message Bruce Momjian 2008-08-23 18:52:16 Re: [GENERAL] Surprising syntax error

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2008-08-23 19:19:26 Re: proposal sql: labeled function params
Previous Message Pavel Stehule 2008-08-23 19:13:09 Re: proposal sql: labeled function params