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

[codesite-noreply at google.com]

Comment #2 on issue 90 by reid at reidster.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.

Actually (in 1.3.3 at least), it seems that both  
AddGeometryColumn(table_name, ...)
and AddGeometryColumn(schema_name, ...) are wrappers for a third variant,
AddGeometryColumn(catalog_name, schema_name, table_name, ...).

As for a fix: can the RAISE NOTICE on line 2840 of lwpostgis.sql be  
replaced with
RAISE EXCEPTION and line 2841 deleted?

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

That's a minor problem. I wouldn't be too sad if the CONTEXT remained.

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