[postgis-devel] Issue 90 in postgis: AddGeometryColumn inappropriately defaults to current_schema() if given nonexistent schema

[codesite-noreply at google.com]

Comment #1 on issue 90 by ke... at refractions.net: AddGeometryColumn  
inappropriately defaults to current_schema() if given nonexistent schema
http://code.google.com/p/postgis/issues/detail?id=90

This is because this function is a wrapper for AddGeometryColumn(table_name,
column_name, srid, type, dimension), where the schemaname is obtained from  
the search
path.  You'd prefer that this is not the case?  The alternative would be  
duplicate
the code to the schema-qualified variant and simply error on an incorrect  
schemaname.
  If others are with you on this behaviour, it's certainly possible to  
change this.

As for the CONTEXT messages: whenever you raise a notice or error in  
plpgsql, a
context message is also displayed.  Unless someone knows how to separate  
this verbose
debugging information from a regular notice or error message, this is the  
best we can
do at the moment with plpgsql.  I suppose we could move these functions to  
C and
write error messages exactly as we see fit, but most people haven't seen  
the need for
that yet.

Hope this helps,
Kevin

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