Re: Case Sensitivity

-----BEGIN PGP SIGNED MESSAGE-----

I don't actually use Derby, not being a Java person, but I *have* used
MySQL for years.  The case-sensitivity issue has bitten me before as
well, but in the other direction:

Satheesh Bandaram wrote:

> I don't think Derby has a property to create a database case
> insensitive. Why exactly do you need the database to be case
> insensitive? Derby has string functions to convert data to upper case or
> lower case, so it is possible for the application to store data in one
> case. (Either upper only or lower only by converting at the input time)
> All the searches after the database is created can then happen in that case.

There's case-sensitive, case-aware/case-preserving, and case-insensitive.
Is it actually the data that should be regarded as case-insensitive, or
search operations?  Case sensitivity makes a difference in collation results,
and I think that can be compounded in some non-ISO-8859-1 character sets.

For comparison, MySQL stores all data verbatim -- that is, case-sensitive.
By default, stringish search operations (WHERE foo LIKE 'bar%') are case
insensitive.  They can be made case-sensitive by labelling one of the
comparison operands as binary, either in the column definition (if appropriate)
or in the search expression (WHERE foo LIKE BINARY 'bar%').

See http://dev.mysql.com/doc/mysql/en/case-sensitivity.html

For what it's worth..
- --
#ken    P-)}

Ken Coar, Sanagendamgagwedweinini  http://Ken.Coar.Org/
Author, developer, opinionist      http://Apache-Server.Com/

"Millennium hand and shrimp!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBQh8G55rNPMCpn3XdAQEPjgQA3gEcRky+K1qqLf8SmFAjfbh7ORBYrsKY
MYOVS9r1H2U617wKGQFOUquVKWsN4DdN8PlslzVaXNjYV1ppvDquk4Yl4prH6OV+
VuSGnecTHRVhRT//QhhimPTXZrk/r1q32VTEK4kDQSfuuDkrHYSFJkrH+f7UZGA8
OqxsQ4QUZJs=
=Yla1
-----END PGP SIGNATURE-----