The problem with using colation order is that it's database-wide. If you
then need case-sensitive ordering on some field you're outa luck. If you
could define colation on a per-field basis it would be a bit different.
I'm also not sure what this has to do with advocacy...
On Sun, Jan 15, 2006 at 10:35:28AM -0500, Robert Bernier wrote:
> Guys,
>
> I'm forwarding this email for your comments.
>
> On January 15, 2006 09:51 am, Charles Phares wrote:
> > Hi Robert,
> >
> > Thanks for taking the time to respond. Yet another solution which I
> > was unaware of. Must do a closer read of the documentation! :)
> >
> > The regexp functions are great for doing equality tests, but they
> > will not help with ranged searches or inequality tests. (i.e.
> > greater than or less than)
> >
> > I really require full-feature support for case insensitivity.
> >
> > The project page for CITEXT -- http://gborg.postgresql.org/project/
> > citext/faq/faq.php?faq_id=105 -- claims that PostgreSQL is unable to
> > define the collating sequence of characters. This seems to be the
> > root of my problem. I know that other database systems -- Sybase &
> > Microsoft SQL Server for instance -- use a user selectable server
> > wide collation sequence to implement case insensitivity. This seems
> > to be the best solution for portability and compatibility with other
> > RDBMS systems.
> >
> > What would it take to rally the PostgreSQL community to embrace this
> > problem?
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
