Voting starts in March for the Drupal Association Board election.
Another issue discovered by Privatemsg, while working on:)
Because the default collation for mysql is usually something like utf8_general_ci (ci = case insensitive), it is not possible to define date formats like "d/m/Y" *and* "d/m/y" because it fails with a duplicate key error.
Not sure how to fix, my suggestion would be to replace the UNIQUE index with a normal index.
Or maybe use db_merge() instead of insert to at least avoid these nasty errors. Especially since they could also happen if two modules define the same date format.
Or both, because it could be confusing if you define "d/m/y" and "d/m/Y" and only the first one ever shows up.
PS: This is not Mysql bug or something like that like the other collation issue, it is by definition. That is why all these collations have a _ci suffix..
PASSED: [[SimpleTest]]: [MySQL] 39,753 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 39,731 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 39,708 pass(es). View