| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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 13:04:23 |
| Message-ID: | 20141029130423.GF28859@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> 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.
Alright, I can change things around to make that happen without too much
trouble.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-10-29 13:47:14 | Re: pg_dump/pg_restore seem broken on hamerkop |
| Previous Message | Stephen Frost | 2014-10-29 13:03:17 | Re: Directory/File Access Permissions for COPY and Generic File Access Functions |