Re: [Firebird-devel] Case-insensitive collations

[Peter J. <pj...@wa...>]

Hi Alexandre,

Alexandre Benson Smith <ib...@th...> wrote:
> >Then why don't you implement one or let one commercial programmer spent
> >four commercially paid hours to make your commercial application work
> >commercially?
> I have no knowlodge of C or knew how FB works internally, I have never been
> involved in dbms design/coding, so I think I cannot do it by my self.

But adding a nocase/naccent collation is simple. If it is such important 
commercially, why hasn't one of the commercial vendors added it 
for their own use as a competitive advantage? Isn't capitalism working
in this case?

It's straightforward C code. It's documented. Samples exist.

> Just a side note:
> Don't take my words in any negative or destructive criticism, I don't 
> have full control of the language, so I think sometimes my comments 
> could be interpreted in the wrong way. :-)

And I hope you are not offended by my sometimes sarcastic postings.

> Does not matter if one user typed ith accent and mixed case, the other type
> with accent in upper case, and a lot of records was pumped in the database
> from a DOS app that just uses upper ASCII, he can search it in any way.
> 
> The ability to enter accent chars in mixed case make the reports more 
> candy to read are with a professional look, when you send an invoice to a
> costumer with all caps withou accent it looks ugly.

I do understand now what you want, but I'm still perplexed about the
situation. In my eyes, a mixture of all-uppercase and mixed case, accented
and pure ASCII variants in the database sounds like a data integrity 
nightmare and not as an improvement over all ASCII uppercase.

Regards,
Peter Jacobi