From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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 18:52:16 |
Message-ID: | 200808231852.m7NIqG720627@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Peter Eisentraut wrote:
> >> On Tuesday 01 July 2008 01:39:13 Bruce Momjian wrote:
> >>> Is there a downside to adding "VIEW" in parser/gram.y:privilege_target?
> >>
> >> The SQL standard doesn't specify it. And there is no need for it.
>
> > 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.
OK, removed from TODO.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2008-08-23 19:14:22 | Re: [GENERAL] Surprising syntax error |
Previous Message | Marc Balmer | 2008-08-23 17:56:48 | Re: psql vs. pgadmin3 was:can't get UPDATE ... RETURNING ... INTO ... to compile successfully |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-08-23 18:57:50 | Re: Proposal: new border setting in psql |
Previous Message | Andrew Dunstan | 2008-08-23 18:42:57 | Re: Proposal: new border setting in psql |