utf8_bin collation on UNIQUE columns needs to be used with caution. In latin1
f == F so a duplicate error would be thrown if a user entered in 'F' when 'f' already existed.
With utf8_bin f != F so, make sure to normalize your data before sticking it into the dblayer i.e. put all email addresses, tags, etc in your db as lowercase :)
Thanks for reminding me Peter Z!!
3 comments:
Are there session settings that screw up utf8 string comparisons? I was inserting a unique varchar field from ruby that was the french spelling for "Hotel" (circumflex over the 'o'), and got a duplicate key error. Which was wierd because we had just executed sql to check for the existance of the field and the application was running with no other processes in the system. Additionall, copying the sql to a mysql terminal session and executing it successfully inserted the row.
Why use utf8_bin? Is it faster?
Post a Comment