<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [postgis-devel] 1.3.4?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Paul,<BR>
Works on my 1.3.3 install. <BR>
I even tried this with srids and casting to null to geometry and also dumping to a temp table.<BR>
<BR>
SELECT * INTO tmp FROM (SELECT NULL::geometry UNION ALL<BR>
SELECT ST_GeometryFromText('POLYGON((0 0, 2 0, 2<BR>
2, 0 2, 0 0))',4326)<BR>
UNION ALL<BR>
SELECT NULL::geometry) As foo(g) cross join generate_series(1,10) n<BR>
<BR>
SELECT ST_Union(g) from tmp<BR>
group by n;<BR>
<BR>
<BR>
What was Charlie whining about then? Maybe he can provide an example of where it fails.<BR>
<BR>
Thanks,<BR>
Regina<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: postgis-devel-bounces@postgis.refractions.net on behalf of Paul Ramsey<BR>
Sent: Fri 10/10/2008 2:55 PM<BR>
To: PostGIS Development Discussion<BR>
Subject: Re: [postgis-devel] 1.3.4?<BR>
<BR>
Just a sec. Do our aggregates not already *do* the right thing WRT nulls?<BR>
<BR>
ebc=# select st_astext(st_union(g)) from ( values ('POINT(0 0)'),<BR>
(NULL), ('POINT(1 1)') ) as v(g);<BR>
<BR>
astext<BR>
---------------------<BR>
MULTIPOINT(0 0,1 1)<BR>
(1 row)<BR>
<BR>
ebc=# select astext(st_union(g)) from ( values ('POLYGON((0 0, 2 0, 2<BR>
2, 0 2, 0 0))'), (NULL), ('POLYGON((1 1, 1 3, 3 3, 3 1, 1 1))') ) as<BR>
v(g);<BR>
astext<BR>
------------------------------------------------<BR>
POLYGON((1 2,1 3,3 3,3 1,2 1,2 0,0 0,0 2,1 2))<BR>
(1 row)<BR>
<BR>
<BR>
On Mon, Oct 6, 2008 at 3:52 AM, Mark Cave-Ayland<BR>
<mark.cave-ayland@siriusit.co.uk> wrote:<BR>
> Paul Ramsey wrote:<BR>
>><BR>
>> OK, Mark's tickets are closed.<BR>
>><BR>
>> That just leaves the handling of NULL and = and ST_Equals as issues.<BR>
>> I'm inclined to deal with *none* of these, since they all change<BR>
>> behavior, which is not good for a point release. However, if people<BR>
>> are convinced that certain of these behaviors are UNAMBIGUOUSLY WRONG,<BR>
>> then we could change them.<BR>
>><BR>
>> I can see changing the aggregates to be more NULL savvy as one of those<BR>
>> cases.<BR>
>><BR>
>> P.<BR>
><BR>
> +1. For 1.3 let's look at mimicking the standard aggregate behaviour with<BR>
> respect to NULLs and leave the =/ST_Equals() debate for a later release.<BR>
><BR>
><BR>
> ATB,<BR>
><BR>
> Mark.<BR>
><BR>
> --<BR>
> Mark Cave-Ayland<BR>
> Sirius Corporation - The Open Source Experts<BR>
> <A HREF="http://www.siriusit.co.uk">http://www.siriusit.co.uk</A><BR>
> T: +44 870 608 0063<BR>
> _______________________________________________<BR>
> postgis-devel mailing list<BR>
> postgis-devel@postgis.refractions.net<BR>
> <A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
><BR>
_______________________________________________<BR>
postgis-devel mailing list<BR>
postgis-devel@postgis.refractions.net<BR>
<A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>