From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | Malcontent null <malcontent(at)msgto(dot)com>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Why Not MySQL? |
Date: | 2000-05-03 11:51:44 |
Message-ID: | 391012D0.D06B42F4@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker wrote:
>
> On Wed, 3 May 2000, Hannu Krosing wrote:
>
> > Malcontent null wrote:
> > >
> > > >Anyway, so the larger class of problem is for the Sybase/M$ user who
> > > >relies on case insensitive queries (which *are* available in Postgres)
> >
> > Maybe the right place to introduce case-insensitiveness would be in ODBC
> > driver then ?
> >
...
> > > 2) Case insensitive queries.
> >
> > Probably only the Access subset ("like", "order by", maybe even "=" ?)
>
> don't we have a 'lower()' function?
>
> SELECT * FROM <table> WHERE field ~* 'this string' ORDER BY lower(field);?
>
> or
>
> SELECT * FROM <table> WHERE lower(field) = lower('StriNg');
That's what I meant by introducing pushing the case-insensitiveness into ODBC,
so that the MS Access program can be made case-insensitive automatically by
A) rewriting the queries to use lower()
or
B) by using case-insensitive operators where possible.
----------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-05-03 12:27:16 | Re: Why Not MySQL? |
Previous Message | Magnus Hagander | 2000-05-03 11:45:32 | RE: Why Not MySQL? |