joseph wrote:
> 2006-04-01 (토), 21:15 -0500, Robert Treat 쓰시길:
>> On Saturday 01 April 2006 17:26, Brendan Duddridge wrote:
...
>> Improved collation support is being worked on but it's a complex problem so
>> there's no realt ETA. (Developers interested in helping out our encouraged
>> to
>> se
2006-04-01 (토), 21:15 -0500, Robert Treat 쓰시길:
> On Saturday 01 April 2006 17:26, Brendan Duddridge wrote:
> > We used to use FrontBase for our databases, but we have since
> > switched to PostgreSQL for
> > performance reasons. However, FrontBase did have very nice collation
> > support.
> >
> > T
joseph wrote:
...
> I was on the postgres lists about 1 1/2 years ago, since then i haven't
> been on then. when there was a question about modifying the way
> postgres does collation and supports character sets on a database (as
> opposed to table, or column-level manner) there was much clammer f
2006-04-01 (토), 19:26 -0700, Brendan Duddridge 쓰시길:
> Excellent. I've just downloaded citext and I'll try it out. Are there
> any problems with it?
> It seems like this should just be added as a default data type to
> PostgreSQL.
>
> Thanks,
>
> ___
Excellent. I've just downloaded citext and I'll try it out. Are there
any problems with it?
It seems like this should just be added as a default data type to
PostgreSQL.
Thanks,
Brendan Duddridge | CTO | 403-277-5591 x24 |
On Saturday 01 April 2006 17:26, Brendan Duddridge wrote:
> We used to use FrontBase for our databases, but we have since
> switched to PostgreSQL for
> performance reasons. However, FrontBase did have very nice collation
> support.
>
> To get case insensitive searches (even on UTF-8 data), all you
We used to use FrontBase for our databases, but we have since
switched to PostgreSQL for
performance reasons. However, FrontBase did have very nice collation
support.
To get case insensitive searches (even on UTF-8 data), all you had to
do was alter the column
and set its collation to 'CAS
