hmm, playing with this. For UTF8, the collation options are utf8_bin and then a series of language specific _ci options.
for ascii, there are choices of ascii_bin and ascii_general_ci etc. On Apr 20, 2010, at 12:32 PM, Robert Garcia wrote: > MySQL is not case insensitive. MySQL can EITHER be case sensitive, or case > insensitive. > > When you setup a database, or table, or even at the column level, there is a > COLLATION option. So if you are using encoding of UTF8, then you are probably > using collation of utf8_general_ci. That "ci" on the end, means "case > insensitive". If you use utf8_general as your collation, it is CASE > SENSITIVE. You set collation at the default level for each database, but you > can change a table default, and you can even set this per column if > necessary. Generally, it is good practice to make password CASE SENSITIVE. > > -- > > Robert Garcia > President - BigHead Technology > VP Application Development - eventpix.com > 15520 Coutelenc Rd > Magalia, Ca 95954 > ph: 530.645.4040 x222 fax: 530.645.4040 > rgar...@bighead.net - rgar...@eventpix.com > http://bighead.net/ - http://eventpix.com/ > > On Apr 20, 2010, at 11:09 AM, Roland Dumas wrote: > >> and the follow-up >> >> witango is case insensitive. seems that mysql is also case insensitive. >> >> How do I set a look-up that is case sensitive? So that password AAAA is not >> the same as aaaa? >> ________________________________________________________________________ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
