[postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema

[codesite-noreply at google.com]

Comment #1 on issue 72 by mark.cav... at siriusit.co.uk: ST_Estimated_Extent  
sometimes returns null if table exists but not in current schema
http://code.google.com/p/postgis/issues/detail?id=72

Hmmm. The problem with this is that "SELECT current_schema()" returns the  
first named
schema within the search_path, and so any other schemas are ignored :(

The only fix for this will be to add an extra schema parameter to
st_estimated_extent() so that it will take parameters in the form of  
(schema, table,
column) and deprecate the 2 parameter version. I don't mind doing the work,  
however
is it possible to clearly mark functions as deprecated in the documentation  
to
dissuade people from using the old version?


ATB,

Mark.


-- 
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