[postgis-devel] Typmod Goodness

[Chris Hodgson]

I'm not sure if you need the view which is limited by the search path - 
but I think limiting it to tables the user has access to makes sense.

On the other hand, is there actually any sensitive data visible in the 
geo(metry|graphy)_columns table? Does it need to be limited at all?

Chris

Kevin Neufeld wrote:
> 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_objrelschema.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