[postgis-users] possible bug: function st_asgeojson(geometry) is not unique

[Paragon Corporation]

In the postgis_upgrade_20_minor.sql file,  there are a bunch of drop
commands at the end.  Just run those and you should be fine.

 Regina
http://www.postgis.us



> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net 
> [mailto:postgis-users-bounces at postgis.refractions.net] On 
> Behalf Of Tom van Tilburg
> Sent: Wednesday, July 11, 2012 3:54 AM
> To: postgis-users at postgis.refractions.net
> Subject: Re: [postgis-users] possible bug: function 
> st_asgeojson(geometry) is not unique
> 
> Thanks Regina and Strk for the enlightment on this.
> I will definately stay with the old-fashioned way then, since 
> I use release candidates quite often and prefer to be bitten 
> as least as possible.
> 
> A final question:
>      Provided that I had a fresh postgis extension on my 
> database but contaminated it by using a restore from data 
> that included postgis stuff, what would be the best way to 
> clean up my current database?
> 
> Best regards,
>   Tom
> 
> 
> 
> On 11-7-2012 2:53, Paragon Corporation wrote:
> > The only issue I see with CREATE EXTENSION at this point is that if 
> > you want to use the subversion releases because they don't have 
> > extension version points (which CREATE EXTENSION requires freeze 
> > points) , it's not upgradeable.  I have a work around for 
> that issue 
> > which I'm experimenting with. That only affects people who want to 
> > live on the edge like strk.
> >
> > If you always go with released versions, it works just 
> dandy from my 
> > experience.  So in a nut-shell its fine for production use, 
> just hard 
> > to use for interim synching with repository version.
> >
> > strk is just against it because he got bitten once early on 
> and he had 
> > a mixed bag of stuff anyway.
> >
> > As far as upgrading from say 1.5.  If you did an unclean upgrade -- 
> > brought over junk and installed on top of a clean postgis 2.0, YOU 
> > NEED to run the postgis_upgrade_minor script or you'll get 
> ambiguous 
> > function calls as you've experienced.
> >
> > Hope that helps,
> > Regina
> > http://www.postgis.us
> >
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: postgis-users-bounces at postgis.refractions.net
> >> [mailto:postgis-users-bounces at postgis.refractions.net] On 
> Behalf Of 
> >> Tom van Tilburg
> >> Sent: Tuesday, July 10, 2012 6:33 AM
> >> To: postgis-users at postgis.refractions.net
> >> Subject: Re: [postgis-users] possible bug: function
> >> st_asgeojson(geometry) is not unique
> >>
> >> On 10-7-2012 12:16, Sandro Santilli wrote:
> >>>> Also I see no double functions in public.functions nor are there 
> >>>> functions in any other place installed in the database.
> >>> select * from pg_proc where proname = 'st_asgeojson'; (I
> >> have 5 rows)
> >> Seems I spoke too soon.. I just created a brand new empty database 
> >> and added postgis by extension.
> >> It worked correctly.
> >>
> >> The previous database was also new but I imported a lot of 
> data that 
> >> came from an earlier postgis database. Seems I accidently 
> copied some 
> >> postgis functions somewhere because "select * from pg_proc where 
> >> proname = 'st_asgeojson';"
> >> returned 11 rows (!).
> >>
> >> Thanks for your input!
> >>
> >> P.S. Do I understand correctly that CREATE EXTENSION is not a 
> >> preferred method for postgis?
> >> _______________________________________________
> >> postgis-users mailing list
> >> postgis-users at postgis.refractions.net
> >> http://postgis.refractions.net/mailman/listinfo/postgis-users
> >>
> >
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-users
> 
> 
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>