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

[codesite-noreply at google.com]

Comment #3 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

> Actually (in 1.3.3 at least), it seems that both  
AddGeometryColumn(table_name, ...)

Yup, you're right, I was just simplifying my response.

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

Ah, I see what you're saying... yup, that works.  You should note that this  
has
already been fixed in SVN trunk.  This function was redone to remove all  
references
to current_schema() in favour of pg_table_is_visible() a while back.
http://code.google.com/p/postgis/issues/detail?id=74&can=1

If you want this fixed in your 1.3 branch, apply the attached patch.  I  
don't think
we can actually apply this patch to SVN since this is a behavioural change  
(albeit
small) to the function.  I would apply this to 1.4, but this has already  
been addressed.

If it ok with you, I'll close this ticket.

Cheers,
Kevin



Attachments:
	lwpostgis.sql.in.patch  449 bytes

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