From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WITH CHECK and Column-Level Privileges |
Date: | 2014-09-26 15:35:09 |
Message-ID: | 20140926153509.GO16422@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Stephen Frost (sfrost(at)snowman(dot)net) wrote:
> * Stephen Frost (sfrost(at)snowman(dot)net) wrote:
> > > Is there similar problems with unique or exclusion constraints?
> >
> > That's certainly an excellent question.. I'll have to go look.
>
> Looks like there is an issue here with CHECK constraints and NOT NULL
> constraints, yes. The uniqueness check complains about the key already
> existing and returns the key, but I don't think that's actually a
> problem- to get that to happen you have to specify the new key and
> that's what is returned.
Yeah, I take that back. If there is a composite key involved then you
can run into the same issue- you update one of the columns to a
conflicting value and get back the entire key, including columns you
shouldn't be allowed to see.
Ugh.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2014-09-26 16:12:22 | Re: BRIN indexes - TRAP: BadArgument |
Previous Message | Stephen Frost | 2014-09-26 15:17:28 | Re: WITH CHECK and Column-Level Privileges |