On Mar 1, 2010, at 9:15 AM, Michael Gould wrote:
>=20
> The following bug has been logged online:
>=20
> Bug reference: 5356
> Logged by: Michael Gould
> Email address: mgould@intermodalsoftwaresolutions.net
> PostgreSQL version: 8.4.2
> Operating system: Windows 2008 R2 Server, Windows 7 x64
> Description: citext not acting like case insensitive search
> Details:=20
>=20
> When we run the following query, we return no results.
>=20
> Select citystateinfoid from iss.citystateinfo where cityname =3D
> 'JACKSONVILLE' and statecode =3D 'FL';
>=20
> However this does work
>=20
> Select citystateinfoid from iss.citystateinfo where cityname =3D
> 'Jacksonville' and statecode =3D 'FL'
>=20
> The second query is how the data is actually stored. I've already forwar=
ded
> our ddl to david wheeler.
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 n=
ot when they're in some other schema? Is `=3D` resolving to `TEXT =3D TEXT`=
if the "iss" schema isn't in the search path?
Michael, does this work?
Select citystateinfoid from iss.citystateinfo where cityname iss.=3D
'JACKSONVILLE' and statecode iss.=3D 'FL';
Best,
David
