Re: patch for type privileges
Peter Eisentraut <peter_e@gmx.net>
From: Peter Eisentraut <peter_e@gmx.net>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-12-01T21:19:04Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Support range data types.
- 4429f6a9e3e1 9.2.0 cited
On mån, 2011-11-28 at 14:25 -0600, Merlin Moncure wrote: > On Tue, Nov 15, 2011 at 2:23 PM, Peter Eisentraut <peter_e@gmx.net> wrote: > > The basics here are mainly informed by the SQL standard. One thing from > > there I did not implement is checking for permission of a type used in > > CAST (foo AS type). This would be doable but relatively complicated, > > and in practice someone how is not supposed to be able to use the type > > wouldn't be able to create the cast or the underlying cast function > > anyway for lack of access to the type. > > I'm not quite following that: with your patch are you or are you not > prohibited from utilizing casts? In other words, if you didn't have > USAGE priv, what would happen if you tried this: > > CREATE VIEW v AS SELECT null::restricted_type::text; ? This is not affected by my patch, so it would do whatever it did before.