Re: bit|varbit #, xor operator - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: bit|varbit #, xor operator
Date
Msg-id 9adb4799-3f9d-69c2-a890-99d59b9d2128@BlueTreble.com
Whole thread Raw
In response to Re: bit|varbit #, xor operator  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bit|varbit #, xor operator  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On 10/17/16 11:29 AM, Tom Lane wrote:
> Jim Nasby <Jim.Nasby@bluetreble.com> writes:
>> On 10/16/16 3:13 PM, Tom Lane wrote:
>>>> Related to this I'd also like to add a boolean XOR operator as that's a
>>>> relatively common request/question.
>
>>> We have boolean XOR; it's spelled "<>".
>
>> I always forget about that...
>
> Maybe it should be mentioned explicitly in the docs.

Hrm, went to go add it and it appears we don't have a section for 
boolean type operators. I guess I should add it to 9.1?

>> though, it doesn't work for boolean arrays.
>
> Define doesn't work?

I would expect array[true, false] XOR array[true, true] to return 
array[false, true], but <> just returns a single true (since the arrays 
are !=).

Though, I guess what would make the most sense there is a map function 
that would apply an operator or function to every element of a set of 
arrays. But I don't see any way to do that without major changes to how 
anyarray works.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: process type escape for log_line_prefix
Next
From: Tom Lane
Date:
Subject: Re: Add PGDLLEXPORT to PG_FUNCTION_INFO_V1