| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres case insensitive searches |
| Date: | 2013-06-29 17:38:24 |
| Message-ID: | 51CF1B90.4040207@hogranch.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general |
On 6/29/2013 9:24 AM, bhanu udaya wrote:
> Upper and Lower functions are not right choice when the table is > 2.5
> million and where we also have heavy insert transactions.
>
> I doubt, if we can cache the table if there are frequent
> inserts/updates. The good idea would be to get the DB to case
> insenstive configuration like SQL Server. I would go for this
> solution, if postgres supports.
you need an INDEX on lower(field) or upper(field). this is only
computed when values are inserted.
if you like a specific feature of SQL Server, then by all means, use SQL
Server. postgres does not and will not support automatic case
insensitive data.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-06-29 19:08:15 | Re: Postgres case insensitive searches |
| Previous Message | bhanu udaya | 2013-06-29 16:24:03 | Re: [GENERAL] Postgres case insensitive searches |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-06-29 19:08:15 | Re: Postgres case insensitive searches |
| Previous Message | bhanu udaya | 2013-06-29 16:24:03 | Re: [GENERAL] Postgres case insensitive searches |