| From: | David Wheeler <david(at)creationengines(dot)com> |
|---|---|
| To: | Michael Fork <mfork(at)toledolink(dot)com> |
| Cc: | Anand Raman <araman(at)india-today(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Case insensitive selects? |
| Date: | 2001-02-15 16:28:55 |
| Message-ID: | Pine.LNX.4.21.0102150826080.16929-100000@theory |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 15 Feb 2001, Michael Fork wrote:
> Indexes *can* and *will* be used if you create the appropiate
> functional indexes, i.e:
>
> CREATE INDEX idx_table_field_upper ON table(upper(field));
>
> SELECT field FROM table WHERE upper(field) LIKE upper('some string');
Hmmm...I'd hate to have two indexes on every field I query like this, one
case-senstive, one case-insensitve (like the one you create here). Is
there a configuration option or something that will tell pgsql to do
case-insensitive comparisons (kinda like MS SQL Server has)? That could
save us on indexing overhead, since we want all of our WHERE comparisons
to be case-insensitive, anyway.
I should also not that we're also using --with-multibyte and having all of
our databases use Unicode exclusively.
Thanks!
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2001-02-15 16:29:24 | Re: regular expression substittion function? |
| Previous Message | Tom Lane | 2001-02-15 16:26:42 | Re: cleaning out template1, and what is template0? |