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 ors
TJ O'Donnell wrote:
maybe the aggregator (whoever,whatever that is) handles null args
differently,
not calling the func when the arg is null?
see:
http://www.postgresql.org/docs/8.1/interactive/sql-createaggregate.html
specifically:
"If the state transition function is declared "strict",
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 r
