From: Gregory S. Williamson <gsw@globexplorer.com>
To: pgsql-sql@postgresql.org
Subject: lower/upper functions and strings in searches
Date: Thu, 14 Aug 2003 16:46:08 -0700
Message-ID: <71E37EF6B7DCC1499CEA0316A256832801057071@loki.globexplorer.com> (raw)
I am obviuously doing some newbie trick, and I ordinarily would spend time browing the archives, but the archives.postgresql.org site seems to be absurdly slow.
This is 7.3.3 on a linux box.
I have a bunch of data with state, city, county and country names. When our application does a search for an exact match:
select * from gx_geotowns where l_state = 'NM';
I get back a lot of rows of cities in New Mexico, as expected.
If I try:
select * from gx_geotowns where upper(l_state) = upper('nm');
I get back:
---------+-----------+----------+------------+------+------
(0 rows)
I've used other databases in which a similar statement worked as exepected:
select * from clients
where upper(client_name) = upper("Some client or otheR");
And it finds the row(s) in question ...
I just know I'm overlooking some real obvious thing but for some reason this eludes me. I could see if the search was very slow (the function returns type "text" and the indexed columns are of type CHAR().
If someone could offer help I would appreciate it,
Thanks,
Greg Williamson
DBA GlobeXplorer LLC
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: gsw@globexplorer.com
Subject: Re: lower/upper functions and strings in searches
In-Reply-To: <71E37EF6B7DCC1499CEA0316A256832801057071@loki.globexplorer.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox