[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 codesite-noreply at google.com
Sat Nov 22 23:29:34 PST 2008


Status: Accepted
Owner: robe.... at cityofboston.gov

New issue 72 by robe.... at cityofboston.gov: ST_Estimated_Extent sometimes  
returns null if table exists but not in current schema
http://code.google.com/p/postgis/issues/detail?id=72

What steps will reproduce the problem?
1. Create a schema - say myschema
2. SET search_path to public,myschema;
3. SELECT ST_Estimated_Extent('somegeomtable', 'the_geom');
where the somegeomtable is in myschema schema.

What is the expected output?
Either an error or the estimated extent

What do you see instead? NULL

Note:  If SET search_path to myschema, public
then estimated extent is correctly returned

If SET search_path to public

Then it correctly returns relation "soemgeomtable" does not exist.

So only seems to be an issue if schema is in search path but not the first
schema in search path.

Seems to happen in both 1.3.3 and 1.3.4 SVN.



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



More information about the postgis-devel mailing list