[postgis-devel] New uninstall_postgis.sql script

[Paragon Corporation]

>"Paragon Corporation" <lr at pcorp.us> writes:
>> I've been doing dumping reloading so haven't fully tested.  So its 
>> just the annoying fact that TYPE has no CREATE OR REPLACE like 
>> functions do.  If such a thing existed for TYPES I would expect all of
this would be a non-issue.

> CREATE OR REPLACE what?  It seems unlikely that you need to change the
names of the I/O functions, and you can't change the type's representational
properties if you're hoping to do upgrade-in-place.
> So I'm not really seeing what CREATE OR REPLACE TYPE would buy exactly.

>Replacing the .so doesn't seem to be a problem, so long as you avoided
putting any version numbers into the .so name referenced in the SQL function
definitions.


Tom,

Sorry about that.  For some reason I thought type had the lib name in there.
I see it doesn't.  Doing a quick scan -- It looks like our types definition
and names did not change between 1.3 and 1.4.  So Mark why do you want to
drop them?  Or am I missing something?

Our operators I think use different named functions though.  But that we can
just use a DROP IF EXISTS I presume (if we standardize on 8.2+)

We added new types but did not remove any.

Our function names are exactly the same too -- just that they point to
different lib file. 

So this seems to be much less of an issue than I thought unless I['m missing
something.

Mark -- why do you want to do all this stuff you were talking about?