From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Phil Frost <indigo(at)bitglue(dot)com> |
Subject: | Re: lastval exposes information that currval does not |
Date: | 2006-07-27 17:16:46 |
Message-ID: | 200607271916.47044.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Phil Frost wrote:
> What two things are there?
Well, the subject says "lastval exposes information that currval does
not" while you are talking about schema permissions. I still don't
know what you're really after. One of your posts stated that you have
repeatedly demonstrated ways to overcome some restriction, but there is
actually only one post that contains some SQL that seems to deal with
schemas.
> I think I've already proposed a solution:
> do the schema usage check at the same time as all the other
> permission checks.
This is an oversimplification, because the permission checks are all
done at different times.
> Alternately, document the behavior accurately.
> I've proposed text here too, but the revisions keep missing the
> point. What needs clarification?
I have interpreted your proposed revision as cynical, not as a serious
proposal.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-07-27 17:17:28 | Re: lastval exposes information that currval does not |
Previous Message | Phil Frost | 2006-07-27 16:50:44 | Re: lastval exposes information that currval does not |