[postgis-devel] PostGIS 1.5 regression with GEOS 3.0.3

[Paragon Corporation]

Strk,
Maybe big warning for 3.1 and absolutely no for 3.0.3.

Honestly there is so much glue missing in 3.0.3 that more than half the
stuff that makes PostGIS 1.4 and PostGIS 1.5 great is disabled.  I figure if
you don't
want any of those missing features (e.g. Cascade Union, prepared geometry
etc), why bother upgrading from 1.3.  Save yourself the hassle?  I mean the
upgrade process from 1.3/1.4/1.5 is much more painful than upgrading GEOS.

Let us not forget the fact that even after you upgrade to 3.1 or 3.2 and
don't recompile your PostGIS, some of the new features are still disabled.

And what do you do when you recompile? run the upgrade script? because your
postgis 1.4/1.5 is still not the same great 1.4./1.5 that someone originally
compiling with GEOS 3.1/3.2 has.

Not to mention the headache of having to test said versions during our
testing cycles and all that hackish ifdef stuff that makes the code a bit
more difficult to read.
PostgreSQL 8.3/8.4/8.5  cross GEOS 3.0.3, GEOS 3.1.0, GEOS 3.2.0  

 That is a lot of permutations.

Maybe I'm missing something not being intimately familiar enough with GEOS.
But it seems to me since GEOS 3.2.0 is backward compatible with GEOS
3.1.0/GEOS 3.0.3 why would it be an issue except for dependencies on other
applications which should be using a different so symlink or dll anyway if
they are that concerned about upgrade consequences.

Thanks,
Regina

 

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of strk
Sent: Tuesday, January 12, 2010 1:17 PM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] PostGIS 1.5 regression with GEOS 3.0.3

What about raising big WARNING messages at configure time instead ?

--strk;

On Tue, Jan 12, 2010 at 04:56:54PM +0000, Mark Cave-Ayland wrote:
> Paragon Corporation wrote:
> 
> >+1.  I'd be really happy if you bumped it to 3.2.  Like I said I hate 
> >+the
> >fact that some of the functions we have will not work on lower 
> >versions we claim to support.  I don't think its anything most people 
> >coming new to PostGIS (or not highly familiar with it) will 
> >understand and just causes confusion.
> 
> I think a minimum of 3.1 would be a sensible idea, if only for the 
> fact that we tend to get repeated reports about bugs in GEOS 3.0 
> series. But let's wait and see what Paul and Kevin think.
> 
> 
> ATB,
> 
> Mark.
> 
> --
> Mark Cave-Ayland - Senior Technical Architect PostgreSQL - PostGIS 
> Sirius Corporation plc - control through freedom 
> http://www.siriusit.co.uk
> t: +44 870 608 0063
> 
> Sirius Labs: http://www.siriusit.co.uk/labs 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel

-- 

 Free GIS & Flash consultant/developer      ()  ASCII Ribbon Campaign
 http://foo.keybit.net/~strk/services.html  /\  Keep it simple! 
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel