From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
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 12:27:16 |
Message-ID: | Pine.BSF.4.21.0005030925180.92638-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 ?
>
> > If I may.
> > MS Access for all of it's damnable faults is the single most popular
> > database in the world. There are a whole slew of people who do nothing
> > except access programming and make very good money at it. Postgres is
> > a great candidate as a possible back end database engine for access.
> > This is a big possible application for postgres. To be usable for this
> > purpose however it needs a few things.
> > 1) Longer object names (I guess this is possible via a DEFINE)
>
> How long should they be ?
>
> > 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');
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-05-03 12:30:07 | Re: Corruption (Was: Re: Why Not MySQL?) |
Previous Message | Hannu Krosing | 2000-05-03 11:51:44 | Re: Why Not MySQL? |