[postgis-devel] 1.3.4?

[Paul Ramsey]

Just a sec. Do our aggregates not already *do* the right thing WRT nulls?

ebc=# select st_astext(st_union(g)) from ( values ('POINT(0 0)'),
(NULL), ('POINT(1 1)') ) as v(g);

       astext
---------------------
 MULTIPOINT(0 0,1 1)
(1 row)

ebc=# select astext(st_union(g)) from ( values ('POLYGON((0 0, 2 0, 2
2, 0 2, 0 0))'), (NULL), ('POLYGON((1 1, 1 3, 3 3, 3 1, 1 1))') ) as
v(g);
                     astext
------------------------------------------------
 POLYGON((1 2,1 3,3 3,3 1,2 1,2 0,0 0,0 2,1 2))
(1 row)


On Mon, Oct 6, 2008 at 3:52 AM, Mark Cave-Ayland
<mark.cave-ayland at siriusit.co.uk> wrote:
> Paul Ramsey wrote:
>>
>> OK, Mark's tickets are closed.
>>
>> That just leaves the handling of NULL and = and ST_Equals as issues.
>> I'm inclined to deal with *none* of these, since they all change
>> behavior, which is not good for a point release.  However, if people
>> are convinced that certain of these behaviors are UNAMBIGUOUSLY WRONG,
>> then we could change them.
>>
>> I can see changing the aggregates to be more NULL savvy as one of those
>> cases.
>>
>> P.
>
> +1. For 1.3 let's look at mimicking the standard aggregate behaviour with
> respect to NULLs and leave the =/ST_Equals() debate for a later release.
>
>
> ATB,
>
> Mark.
>
> --
> Mark Cave-Ayland
> Sirius Corporation - The Open Source Experts
> http://www.siriusit.co.uk
> T: +44 870 608 0063
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>