Comment #2 on issue 3670 by [email protected]: scmtools repository
unique constraint path:local prevents using mysql 5.5 with wide charsets
https://code.google.com/p/reviewboard/issues/detail?id=3670
I don't think we can support utf32 or utf8mb4. Is there a reason plain
ol' utf8 can't be used?
Well in prevents using anything outside of the BMP. Things like emoji,
mathematical symbols, musical symbols live on the SMP. Using utf8, it's
impossible to store these characters in review requests, reviews, comments,
etc.
Since django doesn't let you be choosy about these things, the only way to
enable them anywhere by default is to enable them everywhere by default.
I suppose I can be pickier about which tables and columns we convert -- it
might be unlikely that the path will contain these characters.
Maybe I should really just get around to looking into converting our db to
postgres...
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.
