3 grammar
source | link

As the previous answer, character set is a set of characters (letters, numbers, ideograms etc.) assigned to a number; to be able to see them, you must have the font (the small "pictures" we read). They were important using LatinX, because for each X, the same number (byte) could refer to a different character.

Nowadays it's more important to select the encoding: the standard is UTF-8, the most successful representation of Unicode (compatible with ASCII but so flexible to include all language, even Chinese and Japanese) and W3C standard. In other words, it includes all character sets.

Collation: this is an old-fashion word, derived from Latin. It means: compare a copy (manuscript) with the original to find differences (errors or changes). It was very useful in the past, but now it's almost an archaicism because our documents and books are written using computers and the copy is always identical to the original. Example: in Italian (derived from latin) there is the verb "collazionare", but it's in the dictionaries and nobody uses it.

So, the collation defines the behaviour of comparison operators: =, >, <, <=, >= ...

Of course those operators are used to decide if two strings are the same, or if a word is "greater" than another one, very important if we want to sort. The letters are not in the same order for every language, so a word can be greater than another one using a collation, but not using another one. See [1] for a practical example.

  • the "bin" collations are the most strict: SELECT "b" = "B" => FALSE

  • the "ci" collations are not case sensitive: SELECT "b" = "B" => TRUE

  • the "general" tend to ignore some differences: SELECT "a" = "à" => TRUE

  • other are specific for one or more languages. Example "swedish" (I don't know why swedish it'sis often a default)

I am still searching for a website where the behaviour of every collation is listeddescribed in detail... those examples are due to my experience.

[1] http://www.olcot.co.uk/sql-blogs/revised-difference-between-collation-sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as

As the previous answer, character set is a set of characters (letters, numbers, ideograms etc.) assigned to a number; to be able to see them, you must have the font (the small "pictures" we read). They were important using LatinX, because for each X, the same number (byte) could refer to a different character.

Nowadays it's more important to select the encoding: the standard is UTF-8, the most successful representation of Unicode (compatible with ASCII but so flexible to include all language, even Chinese and Japanese) and W3C standard. In other words, it includes all character sets.

Collation: this is an old-fashion word, derived from Latin. It means: compare a copy (manuscript) with the original to find differences (errors or changes). It was very useful in the past, but now it's almost an archaicism because our documents and books are written using computers and the copy is always identical to the original. Example: in Italian (derived from latin) there is the verb "collazionare", but it's in the dictionaries and nobody uses it.

So, the collation defines the behaviour of comparison operators: =, >, <, <=, >= ...

Of course those operators are used to decide if two strings are the same, or if a word is "greater" than another one, very important if we want to sort. The letters are not in the same order for every language, so a word can be greater than another one using a collation, but not using another one. See [1] for a practical example.

  • the "bin" collations are the most strict: SELECT "b" = "B" => FALSE

  • the "ci" collations are not case sensitive: SELECT "b" = "B" => TRUE

  • the "general" tend to ignore some differences: SELECT "a" = "à" => TRUE

  • other are specific for one or more languages. Example "swedish" (I don't know why swedish it's often a default)

I am still searching for a website where the behaviour of every collation is listed in detail... those examples are due to my experience.

[1] http://www.olcot.co.uk/sql-blogs/revised-difference-between-collation-sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as

As the previous answer, character set is a set of characters (letters, numbers, ideograms etc.) assigned to a number; to be able to see them, you must have the font (the small "pictures" we read). They were important using LatinX, because for each X, the same number (byte) could refer to a different character.

Nowadays it's more important to select the encoding: the standard is UTF-8, the most successful representation of Unicode (compatible with ASCII but so flexible to include all language, even Chinese and Japanese) and W3C standard. In other words, it includes all character sets.

Collation: this is an old-fashion word, derived from Latin. It means: compare a copy (manuscript) with the original to find differences (errors or changes). It was very useful in the past, but now it's almost an archaicism because our documents and books are written using computers and the copy is always identical to the original. Example: in Italian (derived from latin) there is the verb "collazionare", but it's in the dictionaries and nobody uses it.

So, the collation defines the behaviour of comparison operators: =, >, <, <=, >= ...

Of course those operators are used to decide if two strings are the same, or if a word is "greater" than another one, very important if we want to sort. The letters are not in the same order for every language, so a word can be greater than another one using a collation, but not using another one. See [1] for a practical example.

  • the "bin" collations are the most strict: SELECT "b" = "B" => FALSE

  • the "ci" collations are not case sensitive: SELECT "b" = "B" => TRUE

  • the "general" tend to ignore some differences: SELECT "a" = "à" => TRUE

  • other are specific for one or more languages. Example "swedish" (I don't know why swedish is often a default)

I am still searching for a website where the behaviour of every collation is described in detail... those examples are due to my experience.

[1] http://www.olcot.co.uk/sql-blogs/revised-difference-between-collation-sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as

2 details
source | link

As the previous answer, character set is a set of characters (letters, numbers, ideograms etc.); assigned to a number; to be able to see them, you must have the font (the small "pictures" we read). They were important using LatinX, because for each X, the same number (byte) could refer to a different character.

Nowadays it's more important to select the encoding: nowadays, the standard is UTF-8, the most successfullsuccessful representation of Unicode (compatible with ASCII but so flexible to include all language, even Chinese and Japanese) and W3C standard. In other words, it includes all character sets.

Collation: this is an unusedold-fashion word/verb, derived from Latin. It means: compare a copy (manuscript) with the original to find differences (errors or changes). It was very useful in the past, but now it's almost an archaicism because our documents and books are written using computers and the copy is always identical to the original. Example: in Italian (derived from latin) there is the verb "collazionare", but it's in the dictionaries and nobody uses it.

So, the collation defines the behaviour of comparison operators: =, >, <, <=, >= ...

Of course those operators are used to decide if two strings are the same, or if a word is "greater" than another one, very important if we want to sort. The letters are not in the same order for every language, so a word can be greater than another one using a collation, but not using another one. See [1] for a practical example.

  • the "bin" collations are the most strict: SELECT "b" = "B" => FALSE

  • the "ci" collations are not case sensitive: SELECT "b" = "B" => TRUE

  • the "general" tend to ignore some differences: SELECT "a" = "à" => TRUE

  • other are specific for one or more languages. Example "swedish" (I don't know why swedish it's often a default)

I am still searching for a website where the behaviour of every collation is listed in detail... those examples are due to my experience.

[1] http://www.olcot.co.uk/sql-blogs/revised-difference-between-collation-sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as

As the previous answer, character set is a set of characters (letters, numbers, ideograms etc.); it's important to select the encoding: nowadays, the standard is UTF-8, the most successfull representation of Unicode (compatible with ASCII but so flexible to include all language, even Chinese and Japanese) and W3C standard.

Collation: this is an unused word/verb, derived from Latin. It means: compare a copy (manuscript) with the original to find differences (errors or changes). It was very useful in the past, but now it's almost an archaicism because our documents and books are written using computers and the copy is always identical to the original. Example: in Italian (derived from latin) there is the verb "collazionare", but it's in the dictionaries and nobody uses it.

So, the collation defines the behaviour of comparison operators: =, >, <, <=, >= ...

Of course those operators are used to decide if two strings are the same, or if a word is "greater" than another one, very important if we want to sort. The letters are not in the same order for every language, so a word can be greater than another one using a collation, but not using another one. See [1] for a practical example.

  • the "bin" collations are the most strict: SELECT "b" = "B" => FALSE

  • the "ci" collations are not case sensitive: SELECT "b" = "B" => TRUE

  • the "general" tend to ignore some differences: SELECT "a" = "à" => TRUE

I am still searching for a website where the behaviour of every collation is listed in detail... those examples are due to my experience.

[1] http://www.olcot.co.uk/sql-blogs/revised-difference-between-collation-sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as

As the previous answer, character set is a set of characters (letters, numbers, ideograms etc.) assigned to a number; to be able to see them, you must have the font (the small "pictures" we read). They were important using LatinX, because for each X, the same number (byte) could refer to a different character.

Nowadays it's more important to select the encoding: the standard is UTF-8, the most successful representation of Unicode (compatible with ASCII but so flexible to include all language, even Chinese and Japanese) and W3C standard. In other words, it includes all character sets.

Collation: this is an old-fashion word, derived from Latin. It means: compare a copy (manuscript) with the original to find differences (errors or changes). It was very useful in the past, but now it's almost an archaicism because our documents and books are written using computers and the copy is always identical to the original. Example: in Italian (derived from latin) there is the verb "collazionare", but it's in the dictionaries and nobody uses it.

So, the collation defines the behaviour of comparison operators: =, >, <, <=, >= ...

Of course those operators are used to decide if two strings are the same, or if a word is "greater" than another one, very important if we want to sort. The letters are not in the same order for every language, so a word can be greater than another one using a collation, but not using another one. See [1] for a practical example.

  • the "bin" collations are the most strict: SELECT "b" = "B" => FALSE

  • the "ci" collations are not case sensitive: SELECT "b" = "B" => TRUE

  • the "general" tend to ignore some differences: SELECT "a" = "à" => TRUE

  • other are specific for one or more languages. Example "swedish" (I don't know why swedish it's often a default)

I am still searching for a website where the behaviour of every collation is listed in detail... those examples are due to my experience.

[1] http://www.olcot.co.uk/sql-blogs/revised-difference-between-collation-sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as

1
source | link

As the previous answer, character set is a set of characters (letters, numbers, ideograms etc.); it's important to select the encoding: nowadays, the standard is UTF-8, the most successfull representation of Unicode (compatible with ASCII but so flexible to include all language, even Chinese and Japanese) and W3C standard.

Collation: this is an unused word/verb, derived from Latin. It means: compare a copy (manuscript) with the original to find differences (errors or changes). It was very useful in the past, but now it's almost an archaicism because our documents and books are written using computers and the copy is always identical to the original. Example: in Italian (derived from latin) there is the verb "collazionare", but it's in the dictionaries and nobody uses it.

So, the collation defines the behaviour of comparison operators: =, >, <, <=, >= ...

Of course those operators are used to decide if two strings are the same, or if a word is "greater" than another one, very important if we want to sort. The letters are not in the same order for every language, so a word can be greater than another one using a collation, but not using another one. See [1] for a practical example.

  • the "bin" collations are the most strict: SELECT "b" = "B" => FALSE

  • the "ci" collations are not case sensitive: SELECT "b" = "B" => TRUE

  • the "general" tend to ignore some differences: SELECT "a" = "à" => TRUE

I am still searching for a website where the behaviour of every collation is listed in detail... those examples are due to my experience.

[1] http://www.olcot.co.uk/sql-blogs/revised-difference-between-collation-sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as