Re: BUG #5356: citext not acting like case insensitive search

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: "Michael Gould" <mgould(at)intermodalsoftwaresolutions(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5356: citext not acting like case insensitive search
Date: 2010-03-01 18:17:08
Message-ID: 20693.1267467428@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> Michael managed to fix this issue by moving citext to the "public"
> schema. The question is, why would citext operators work in the public
> schema but not when they're in some other schema?

Are they in the search path?

> Michael, does this work?

> Select citystateinfoid from iss.citystateinfo where cityname iss.=
> 'JACKSONVILLE' and statecode iss.= 'FL';

The syntax is OPERATOR(iss.=) not just iss.= ...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-03-01 18:25:28 Re: BUG #5356: citext not acting like case insensitive search
Previous Message Robert Haas 2010-03-01 17:32:53 Re: BUG #4673: pl/PgSQL: Bug, when updating changed composite types.