[postgis-devel] Probe_Geometry_Columns() only in public schema?

[Per-Olof Norén]

Thanks Kevin,
It looks very promising.
I'll give it a try

/P-O

Kevin Neufeld skrev:
> You could try to import the new Populate_Geometry_Columns() that's 
> available in 1.4 into your 1.3.3 database.  One variant of this method 
> takes a table oid which you could use to iterate over all tables in a 
> particular schema.
>
> http://postgis.refractions.net/documentation/manual-svn/Populate_Geometry_Columns.html 
>
>
> The difference between Probe_Geo.. and Populate_Geo... is that probe 
> requires that your geometry columns were originally added to your 
> tables via AddGeometryColumns() (or the table constraints were added 
> manually), populate does not.
>
> -- Kevin
>
> Per-Olof Norén wrote:
>> Hi guys,
>>
>> I have a database where all tables with geometry data is in (8) 
>> different schemas.
>> Having destroyed the data in my geometry_columns table, I looked 
>> around for managment function and found Probe_Geometry_Columns().
>>
>>
>> After running probe_geometry_columns it reports having scanned only 
>> my two tables in the public schema (geometry_columns + spatial_ref_sys)
>>
>> Is this a known limitation on 1.3.3 ?
>> (select postgis_lib_version() => 1.3.3)
>>
>> A suggestion might be to supply a schema name as argument?
>>
>> Regards,
>> Per-Olof
>>
>> _______________________________________________
>> 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