Changes between Version 19 and Version 20 of MySqlDb
- Timestamp:
- Nov 26, 2007, 7:58:39 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MySqlDb
v19 v20 18 18 XXX: I think the above advice on collations is wrong - using a case-insensitive collation does not sound right, and when I used the above command, the indexing process failed when it came to insert a revision which included changes to files with names differing only in case. Recreating the db using the utf8_bin collation allowed things to work as expected. 19 19 ''See also: [comment:ticket:4378:5 #4378], where someone stated the opposite (i.e. that setting the collation mode to utf8_bin was ''not'' enough... Maybe this depends on the type of tables used. Anyway, there's a patch on #4378 that should solve that issue in all cases.'' 20 ''utf8_general_ci is required because MySQL-Python uses the collation to figure out if it is being passed binary or text. See [https://sourceforge.net/tracker/index.php?func=detail&aid=1693363&group_id=22307&atid=374932 bug 1693363]'' 20 21 21 22 To check character set settings for your database, issue command: