Re: [HACKERS] Case insensitivity, and option?

2003-03-23 Thread ow
> select * from table where field ILIKE 'blAH'; -- ;-) > is almost as easy :-) > PS: no, don't do this if you want portability. I think the charset > idea's a better one. > > Ron “select * from table where lower(field)=lower('BLah')” will break portability too in the sense that many DBs (perhaps

Re: [HACKERS] Case insensitivity, and option?

2003-03-12 Thread Ron Mayer
mlw wrote: > ... >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 > ... select * from table where field ILIKE 'blAH'; -- ;-) is almost as easy :-) PS

Re: [HACKERS] Case insensitivity, and option?

2003-03-12 Thread Rod Taylor
On Wed, 2003-03-12 at 13:35, Dwayne Miller wrote: > I know that the MSSQL code works because the default collation sequence > for character fields is case-insensitive. You can change it for each > field independantly to be case sensitive, local specific, etc. I'm not > sure if PG supports a co

Re: [HACKERS] Case insensitivity, and option?

2003-03-12 Thread Dwayne Miller
I know that the MSSQL code works because the default collation sequence for character fields is case-insensitive. You can change it for each field independantly to be case sensitive, local specific, etc. I'm not sure if PG supports a collation sequence attribute on column definitions/indexes.

Re: [HACKERS] Case insensitivity, and option?

2003-03-12 Thread Rod Taylor
On Wed, 2003-03-12 at 12:57, [EMAIL PROTECTED] wrote: > > > > > > --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: > > | s

Re: [HACKERS] Case insensitivity, and option?

2003-03-12 Thread pgsql
> > > --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) bec

Re: [HACKERS] Case insensitivity, and option?

2003-03-12 Thread Rod Taylor
On Wed, 2003-03-12 at 09:03, mlw wrote: > 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 cod

Re: [HACKERS] Case insensitivity, and option?

2003-03-12 Thread Mathieu Arnold
--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 m

[HACKERS] Case insensitivity, and option?

2003-03-12 Thread mlw
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 woul