Re: Unable to compare _bpchar for similarity in WHERE-clause - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: Unable to compare _bpchar for similarity in WHERE-clause
Date
Msg-id 200112151612.fBFGCXA02112@candle.pha.pa.us
Whole thread Raw
In response to Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)
List pgsql-bugs
> Nicolai@ISYS.DK writes:
> > When I try to write an UPDATE where I include a WHERE-clause like:
> > [WHERE something='{"a","b","c"}], where something is a character[], i get
> > the errormessage:[Unable to identify an operator = for types '_bpchar and
> > 'unknown' You will have to retype this query using an explicit cast]
> > The above statement works for text[].
>
> Hmm.  Looks like there is a pg_operator entry for text[] = text[],
> but none for bpchar[] = bpchar[].  This is an oversight, nothing more.
> Feel free to add such an entry --- it can point to the same array-equals
> function as the one for text[].
>
> It's too late to fix this in the standard catalogs for 7.2, but I'll
> make a note for 7.3.

Added to TODO:

    * Add bpchar array comparison

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: stuck spinlock. Aborting. What does this mean?
Next
From: Tom Lane
Date:
Subject: Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)