From: Josh Berkus <josh@agliodbs.com>
To: Gregory S. Williamson <gsw@globexplorer.com>
To: pgsql-sql@postgresql.org
Subject: Re: lower/upper functions and strings in searches
Date: Thu, 14 Aug 2003 17:17:31 -0700
Message-ID: <200308141717.31645.josh@agliodbs.com> (raw)
In-Reply-To: <71E37EF6B7DCC1499CEA0316A256832801057071@loki.globexplorer.com>
References: <71E37EF6B7DCC1499CEA0316A256832801057071@loki.globexplorer.com>
Gregory,
> 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().
Char(what?) ?
if it's, say CHAR(4) that could be your problem;
'NM'::undefined == 'NM '::CHAR
but
'NM'::TEXT != 'NM '::CHAR
so casting everything to the desired type should fix the problem.
and why are you using CHAR, anyway?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, gsw@globexplorer.com
Subject: Re: lower/upper functions and strings in searches
In-Reply-To: <200308141717.31645.josh@agliodbs.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