| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | David Wheeler <david(at)wheeler(dot)net> |
| Cc: | Michael Fork <mfork(at)toledolink(dot)com>, Anand Raman <araman(at)india-today(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Case insensitive selects? |
| Date: | 2001-02-16 19:57:35 |
| Message-ID: | 200102161957.OAA28548@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Wouldn't it be more efficient to just have a single, case-insensitive
> index, and then have the query engine automagically compare to the index
> in a case-insensitive way? I'm assuming that this is the sort of approach
> MS takes, which is why one has to choose the sort order at installation
> time. If I choose case-insensitive Unicode, then I would expect the server
> to do these things for me behind the scenes:
>
Yes, our CREATE INDEX lower(col) already does that, but you do have to
use lower(col) when doing the query.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Wheeler | 2001-02-16 20:05:38 | Re: Case insensitive selects? |
| Previous Message | David Wheeler | 2001-02-16 19:56:08 | Re: Case insensitive selects? |