| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WITH CHECK and Column-Level Privileges |
| Date: | 2014-10-29 12:44:34 |
| Message-ID: | CA+TgmoZO-9jHu9FM_=xPt+2HLUzcmL=waw8qDBAe-zcb+ijcBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 29, 2014 at 8:16 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> suggestions. If the user does not have table-level SELECT rights,
> they'll see for the "Failing row contains" case, they'll get:
>
> Failing row contains (col1, col2, col3) = (1, 2, 3).
>
> Or, if they have no access to any columns:
>
> Failing row contains () = ()
I haven't looked at the code, but that sounds nice, except that if
they have no access to any columns, I'd leave the message out
altogether instead of emitting it with no useful content.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-10-29 12:53:10 | Re: Directory/File Access Permissions for COPY and Generic File Access Functions |
| Previous Message | Robert Haas | 2014-10-29 12:42:47 | Re: TAP test breakage on MacOS X |