| From: | pgsql(at)mohawksoft(dot)com |
|---|---|
| To: | m(at)mat(dot)cc |
| Cc: | pgsql(at)mohawksoft(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Case insensitivity, and option? |
| Date: | 2003-03-12 17:57:11 |
| Message-ID: | 1080.141.154.37.102.1047491831.squirrel@mail.mohawksoft.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>
> --le 12/03/2003 09:03 -0500, mlw écrivait :
> | I was at a client office reviewing some code. They use MSSQL and I |
> noticed that:
> |
> | select * from table where field = 'blah';
> | gave the same results as:
> | select * from table where field = 'BLah';
> |
> | I was shocked. (a) because I know a lot of my code could be easier to
> | write, and (b) that their code would break on every other database I
> am | aware of. Does anyone know about this?
> |
> | Is it practical/desirable for PostgreSQL to have this as a
> configuration | setting?
>
> Well, I quite don't see any difference with writing :
>select * from table where lower(field) = lower('BLah');
That would probably require an extra index, especially if 'field' is a
primary key.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2003-03-12 17:59:10 | Re: Case insensitivity, and option? |
| Previous Message | Peter Eisentraut | 2003-03-12 17:46:14 | Re: Roadmap for FE/BE protocol redesign |