[postgis-devel] Typmod Goodness

[Stephen Frost]

* Paragon Corporation (lr at pcorp.us) wrote:
> Actually I like the idea of having 2 views, because if I have a database
> with a 1000 spatial tables in it, I normally don't care to wait around to
> see everyone else's stuff. 

I'd be alright with filtering things you can't access.

> I believe pg_tables and information_schema.tables do have a filter, but I
> think its based on priviledge (or am I thinking about pg_settings). Steve --
> you happen to know anything about that one way or the other?

pg_catalog tables typically don't filter.  pg_tables isn't filtered.
The information_schema does typically filter, and
information_schema.tables does have a filter on permissions:

pg_has_role(c.relowner, 'USAGE'::text) OR
has_table_privilege(c.oid, 'SELECT'::text) OR
has_table_privilege(c.oid, 'INSERT'::text) OR
has_table_privilege(c.oid, 'UPDATE'::text) OR
has_table_privilege(c.oid, 'DELETE'::text) OR
has_table_privilege(c.oid, 'REFERENCES'::text) OR
has_table_privilege(c.oid, 'TRIGGER'::text)

	Thanks,

		Stephen

> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net
> [mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Kevin
> Neufeld
> Sent: Friday, August 07, 2009 3:52 PM
> To: PostGIS Development Discussion
> Subject: Re: [postgis-devel] Typmod Goodness
> 
> I'm not partial either way, but perhaps it might be an idea to follow
> Oracle's example:
> http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28400/sdo_objrelsch
> ema.htm#i1001937
> 
> Have two views. One to list the geography_columns in the user's search_path,
> and one to list all geography_columns which the user has select access to.
> 
> -- Kevin
> 
> Stephen Frost wrote:
> > * Paragon Corporation (lr at pcorp.us) wrote:
> >> I disagree with the pg_table_is_visible = true addition (if it 
> >> ensures only tables in your search path).
> > 
> > So do I.  I equate 'geometry_columns' and 'geography_columns' to 
> > 'pg_class', 'pg_tables', or 'information_schema.tables', none of which 
> > have any such filter based on current search_path.  That's something 
> > implemented in the client, where necessary and appropriate.
> > 
> > 	Thanks,
> > 
> > 		Stephen
> > 
> > 
> > ----------------------------------------------------------------------
> > --
> > 
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-devel
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
> 
> 
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20090807/8f57f3da/attachment.sig>