Re: Unable to compare _bpchar for similarity in WHERE-clause

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Nicolai(at)ISYS(dot)DK, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Unable to compare _bpchar for similarity in WHERE-clause
Date: 2001-12-15 16:12:33
Message-ID: 200112151612.fBFGCXA02112@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Nicolai(at)ISYS(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-12-15 17:17:19 Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)
Previous Message Tom Lane 2001-12-14 22:31:02 Re: stuck spinlock. Aborting. What does this mean?