Re: aggregate of bitstrings

From: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
To: tjo(at)acm(dot)org
Cc: ggazan(at)ausd(dot)net, pgsql-general(at)postgresql(dot)org
Subject: Re: aggregate of bitstrings
Date: 2006-06-23 01:04:38
Message-ID: 449B3E26.7040006@phlo.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

TJ O'Donnell wrote:
> AHA! I hadn't encountered any null values in my bitstrings.
> and having to include 'where xxx is not null' is rather
> inconvenient and easy to forget.
>
> indeed bitor(B'1000',null) returns null
>
> but as a test, i nulled one row's data (the bitstring column portion only)
> and my orsum without INITCOND returned the proper OR of the remaining
> values
> when including all rows in the aggregate. it did not return null.
Hm.. strange.. I could have sworn that I added the initcond to fix some
null-related issue...
Maybe is was the aggregate returning null where there where no rows
to aggregate.. I'll test this again, I'd actually love to get rid of
that initcond.

greetings, Florian Pflug

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2006-06-23 01:33:28 Re: join on next row
Previous Message Joseph Shraibman 2006-06-23 00:12:36 Idea for vacuuming