RE: Case sensitivity

Oh, I must not have been too clear in the problem/solution I was seeking.
First, I did not know about the ILIKE conditional, thanks.  But, I was not
looking for case insensitivity with literals.

    select * from logins where "Logins"."Login"='rhurst'

The 'logins' in FROM is not the same as 'Logins' in WHERE.  And, PostgreSQL
does not validate all the relations in FROM to match up with what is used in
SELECT / WHERE, so this SQL call is accepted.  Unless I use a hex editor on
the client binary (which isn't a bad idea), I was just suggesting that a
case insensitivity option on the PostgreSQL server and/or the ODBC client
would be choice.  Or even if one exists now?

TIA!


> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr]
> Sent: Saturday, May 12, 2001 3:55am
> To: Robert Hurst
> Subject: Re: [ODBC] Case sensitivity
>
>
> Hello Robert ,
>
> You should try
> select * from logins where Login ilike ='rhurst'
>
> LIKE statement is case sensible,
> ILIKE is not case sensible
>
> For more information, visit
> http://odbc.postgresql.org/docs/index.php?functions-matching.html
>
> Greetings from Jean-Michel POURE, Paris, France
>
> At 18:41 08/05/01 -0400, you wrote:
> >A suggestion for a feature to add to your already wonderful ODBC
> capability.
> >Could you add a boolean option that enables/disables case
> sensitivity with
> >ODBC calls?  Consider this example, a Delphi client sends:
> >
> >         select * from logins where "Logins"."Login"='rhurst'
> >
> >I know it looks ridiculous.  This currently has the ill effect of forcing
> >pgsql to look for the table 'logins' (case sensitive) when only 'Logins'
> >exist!  Wouldn't it be nice if I could set an ignore-case flag for ODBC?
> >
> >
> >Robert Hurst, I.S. Director
> >Butler Hospital · 345 Blackstone Boulevard · Providence, RI 02906
> >Voice: (401) 455-6262 · Pager: (401) 460-4594
> >A Care New England hospital, http://www.carenewengland.org
> >"Any technology distinguishable from magic is insufficiently advanced."
> >
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 5: Have you checked our extensive FAQ?
> >
> >http://www.postgresql.org/users-lounge/docs/faq.html
>