-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql: support database-level collations #16618
Comments
I suggest you to look at DUCET "Default Unicode Collation Element Table" https://en.wikipedia.org/wiki/Unicode_collation_algorithm ICU library has this as "root" collation and I guess go has support for ICU in https://github.com/golang/text repository. ICU has many options for example you can collate with german locale, case and accent insensitive and phonebook sort which is special sorting for used on only german phonebooks. Postgresql has it in version 10 but they didn't support case and accent sensitivity. Main problem with Postgresql was it's used OS libraries for collation handling. This is problematic many ways because collation algorithms updated out of control and indexes became corrupted with changed rules. So they adopt ICU library to be able to version collation algorithm on index. With glibc this is impossible. But they still didn't support case insensitive collations and this is no go for many users uses ORM tools to manage schema and access. MySQL has this since version 5.5, they call utf8mb4. You can look at http://mysqlserverteam.com/new-collations-in-mysql-8-0-0 for what's coming with 8. They made it default for new db. |
Thanks, we already implemented support for collation at the column level via golang/text. |
This is necessary for CockroachDB support: cockroachdb/cockroach#16618 CockroachDB's CREATE DATABASE currently supports only "C" and "C.UTF-8" collations.
This is necessary for CockroachDB support: cockroachdb/cockroach#16618 CockroachDB's CREATE DATABASE currently supports only "C" and "C.UTF-8" collations.
Feature request broken off from #2473 .
Jira issue: CRDB-6061
The text was updated successfully, but these errors were encountered: