#5958 closed (invalid)
mention not to use utf8_bin with MySQLdb in documentation/unicode
| Reported by: | Till Backhaus | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | encoding utf8 unicode str error string mysql mysqldb | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
For those users who are not that familiar with databases and their encoding it would be great if the documentation mentioned that you should not use utf8_bin as collation.
Change History (2)
comment:1 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 18 years ago
For the record, the reason it was suggested not to use utf8_bin is because of an outstanding bug when this collation is used with mysqldb (#2335).
Note:
See TracTickets
for help on using tickets.
Why don't we want utf8_bin as it's case-sensitive (instead of utf8_general_ci which isn't)?