The real reason you want to use NVARCHAR is when you have different languages in the same column, you need to address the columns in T-SQL without decoding, you want to be able to see the data “natively” in SSMS, or you want to standardize on Unicode. If you treat the database as dumb storage, … Read more
Coerce to an accent insensitive collation You’ll also need to ensure both side have the same collation to avoid errors or further coercions if you want to compare against a table variable or temp table varchar column and because the constant value will have the collation of the database Update: only for local variables, not … Read more
IBM’s ICU library does that (and a lot more). It has Python bindings: PyICU. Update: The core difference in sorting between ICU and locale.strcoll is that ICU uses the full Unicode Collation Algorithm while strcoll uses ISO 14651. The differences between those two algorithms are briefly summarized here: http://unicode.org/faq/collation.html#13. These are rather exotic special cases, … Read more
Here is a more complete version based on the Unicode standard. var Latinise={};Latinise.latin_map={“Á”:”A”, “Ă”:”A”, “Ắ”:”A”, “Ặ”:”A”, “Ằ”:”A”, “Ẳ”:”A”, “Ẵ”:”A”, “Ǎ”:”A”, “”:”A”, “Ấ”:”A”, “Ậ”:”A”, “Ầ”:”A”, “Ẩ”:”A”, “Ẫ”:”A”, “Ä”:”A”, “Ǟ”:”A”, “Ȧ”:”A”, “Ǡ”:”A”, “Ạ”:”A”, “Ȁ”:”A”, “À”:”A”, “Ả”:”A”, “Ȃ”:”A”, “Ā”:”A”, “Ą”:”A”, “Å”:”A”, “Ǻ”:”A”, “Ḁ”:”A”, “Ⱥ”:”A”, “Ô:”A”, “Ꜳ”:”AA”, “Æ”:”AE”, “Ǽ”:”AE”, “Ǣ”:”AE”, “Ꜵ”:”AO”, “Ꜷ”:”AU”, “Ꜹ”:”AV”, “Ꜻ”:”AV”, “Ꜽ”:”AY”, “Ḃ”:”B”, “Ḅ”:”B”, “Ɓ”:”B”, “Ḇ”:”B”, … Read more
If you want to change the table default character set and all character columns to a new character set, use a statement like this: ALTER TABLE tbl_name CONVERT TO CHARACTER SET charset_name; So query will be: ALTER TABLE etape_prospection CONVERT TO CHARACTER SET utf8;
The bloke who wrote it was co-head of a Swedish company. Possibly for similar reasons, Microsoft SQL Server’s default language us_english.
SHOW TABLE STATUS shows information about a table, including the collation. For example SHOW TABLE STATUS where name like ‘TABLE_NAME’
It sets how the database server sorts (compares pieces of text). in this case: SQL_Latin1_General_CP1_CI_AS breaks up into interesting parts: latin1 makes the server treat strings using charset latin 1, basically ascii CP1 stands for Code Page 1252 CI case insensitive comparisons so ‘ABC’ would equal ‘abc’ AS accent sensitive, so ‘ü’ does not equal … Read more
change database collation: ALTER DATABASE <database_name> CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci; change table collation: ALTER TABLE <table_name> CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci; change column collation: ALTER TABLE <table_name> MODIFY <column_name> VARCHAR(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci; What do the parts of utf8mb4_0900_ai_ci mean? 3 bytes — utf8 4 bytes — utf8mb4 (new) v4.0 … Read more
To change the default character set and collation of a table including those of existing columns (note the convert to clause): alter table <some_table> convert to character set utf8mb4 collate utf8mb4_unicode_ci; Edited the answer, thanks to the prompting of some comments: Should avoid recommending utf8. It’s almost never what you want, and often leads to … Read more