| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Theo Galanakis <Theo(dot)Galanakis(at)lonelyplanet(dot)com(dot)au> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Mysql to postgres |
| Date: | 2005-04-11 07:02:01 |
| Message-ID: | 22593.1113202921@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Theo Galanakis <Theo(dot)Galanakis(at)lonelyplanet(dot)com(dot)au> writes:
> There may be a way to change the database in postgres to be case
> insensitive. i.e. change some of the operations such as "text=text" to be
> case insensitive. Does this sound Insane?
I think it would be exceedingly unwise to muck with the standard
behavior of a commonly used datatype. What some other people have
done is to invent a variant datatype "citext" that shares most of the
same operations as "text", but has case-insensitive comparisons.
Then you only need to hack your table definitions, not your application
code.
http://gborg.postgresql.org/project/citext/projdisplay.php
I think you could probably also do it by building a locale whose
comparisons are case-insensitive, but I don't know enough about
locales to be sure.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kaminski | 2005-04-11 07:34:33 | Re: pg_dump on remote machine |
| Previous Message | Theo Galanakis | 2005-04-11 06:26:06 | Mysql to postgres |