[postgis-devel] Issue 34 in postgis: .prj creation by pgsql2shp

[codesite-noreply at google.com]

Comment #7 on issue 34 by ke... at refractions.net: .prj creation by pgsql2shp
http://code.google.com/p/postgis/issues/detail?id=34

Interesting use of COALESCE ... seems logical, should work.

But, yes, I agree that when a schema is not provided, you should add a 'AND
pg_table_is_visible((gc.f_table_schema || '.' ||  
gc.f_table_name)::regclass)' filter
to your first query against the geometry_columns table. There could easily  
be
duplicates in the geometry_columns table when strictly looking at  
f_table_name and
f_geometry_column and you may be pulling the SRID that belongs to a  
different table.

You shouldn't have to modify the second query since specifying a non-schema  
qualified
table already defaults to looking just in the user's search_path.

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings