Search
| 1 to 14 of 14 |
MySQL.com Search Results
1. MySQL :: MySQL 5.1 Reference Manual :: 9.1.5.5 Collations Must Be for the Right Character Set
9.1.5.5. Collations Must Be for the Right Character Set Each character set has one or more collations, but each collation is associated with one and only one character set. Therefore, the following statement causes an error message because the latin2_bin collation is not legal with the latin1 character set: mysql> SELECT _latin1 'x' COLLATE latin2_bin; ERROR 1253 (42000): COLLATION 'latin2_bin' is not valid for CHARACTER SET 'latin1'
» http://dev.mysql.com/doc/refman/5.1/en/charset-collation-charset.html
2. MySQL :: MySQL 5.0 Reference Manual :: 9.1.5.5 Collations Must Be for the Right Character Set
9.1.5.5. Collations Must Be for the Right Character Set Each character set has one or more collations, but each collation is associated with one and only one character set. Therefore, the following statement causes an error message because the latin2_bin collation is not legal with the latin1 character set: mysql> SELECT _latin1 'x' COLLATE latin2_bin; ERROR 1253 (42000): COLLATION 'latin2_bin' is not valid for CHARACTER SET 'latin1'
» http://dev.mysql.com/doc/refman/5.0/en/charset-collation-charset.html
3. MySQL :: MySQL 6.0 Reference Manual :: 9.1.5.5 Collations Must Be for the Right Character Set
9.1.5.5. Collations Must Be for the Right Character Set Each character set has one or more collations, but each collation is associated with one and only one character set. Therefore, the following statement causes an error message because the latin2_bin collation is not legal with the latin1 character set: mysql> SELECT _latin1 'x' COLLATE latin2_bin; ERROR 1253 (42000): COLLATION 'latin2_bin' is not valid for CHARACTER SET 'latin1'
» http://dev.mysql.com/doc/refman/6.0/en/charset-collation-charset.html
9.1.5.5. Collations Must Be for the Right Character Set Each character set has one or more collations, but each collation is associated with one and only one character set. Therefore, the following statement causes an error message because the latin2_bin collation is not legal with the latin1 character set: mysql> SELECT _latin1 'x' COLLATE latin2_bin; ERROR 1253 (42000): COLLATION 'latin2_bin' is not valid for CHARACTER SET 'latin1'
» http://dev.mysql.com/doc/refman/5.1-maria/en/charset-collation-charset.html
5. MySQL :: MySQL 5.0 Reference Manual :: 17.3.1.2 Replication and Character Sets
17.3.1.2. Replication and Character Sets The following applies to replication between MySQL servers that use different character sets: If the master uses MySQL 4.1, you must always use the same global character set and collation on the master and the slave, regardless of the MySQL version running on the slave. (These are controlled by the --character-set-server and --collation-server options.) Otherwise, you may get duplicate-key errors on the slave, because a key that is unique in the master character set
» http://dev.mysql.com/doc/refman/5.0/en/replication-features-charset.html
6. MySQL :: MySQL 5.1 Reference Manual :: 19.3.1.2 Replication and Character Sets
19.3.1.2. Replication and Character Sets The following applies to replication between MySQL servers that use different character sets: If the master uses MySQL 4.1, you must always use the same global character set and collation on the master and the slave, regardless of the MySQL version running on the slave. (These are controlled by the --character-set-server and --collation-server options.) Otherwise, you may get duplicate-key errors on the slave, because a key that is unique in the master character set
» http://dev.mysql.com/doc/refman/5.1/en/replication-features-charset.html
7. MySQL :: MySQL 6.0 Reference Manual :: 17.3.1.2 Replication and Character Sets
17.3.1.2. Replication and Character Sets The following applies to replication between MySQL servers that use different character sets: If the master uses MySQL 4.1, you must always use the same global character set and collation on the master and the slave, regardless of the MySQL version running on the slave. (These are controlled by the --character-set-server and --collation-server options.) Otherwise, you may get duplicate-key errors on the slave, because a key that is unique in the master character set
» http://dev.mysql.com/doc/refman/6.0/en/replication-features-charset.html
8. MySQL :: MySQL 5.1 with Maria Reference Manual :: 16.3.1.2 Replication and Character Sets
16.3.1.2. Replication and Character Sets The following applies to replication between MySQL servers that use different character sets: If the master uses MySQL 4.1, you must always use the same global character set and collation on the master and the slave, regardless of the MySQL version running on the slave. (These are controlled by the --character-set-server and --collation-server options.) Otherwise, you may get duplicate-key errors on the slave, because a key that is unique in the master character set
» http://dev.mysql.com/doc/refman/5.1-maria/en/replication-features-charset.html
9. MySQL :: MySQL 5.1 Reference Manual :: 9.1 Character Set Support
9.1. Character Set Support [ +/- ] 9.1.1. Character Sets and Collations in General 9.1.2. Character Sets and Collations in MySQL 9.1.3. Specifying Character Sets and Collations 9.1.4. Connection Character Sets and Collations 9.1.5. Collation Issues 9.1.6. String Repertoire 9.1.7. Operations Affected by Character Set Support 9.1.8. Unicode Support 9.1.9. UTF-8 for Metadata 9.1.10. Column Character Set Conversion 9.1.11. Character Sets and Collations That MySQL Supports MySQL includes character set support th
» http://dev.mysql.com/doc/refman/5.1/en/charset.html
10. MySQL :: MySQL 5.0 Reference Manual :: 9.1 Character Set Support
9.1. Character Set Support [ +/- ] 9.1.1. Character Sets and Collations in General 9.1.2. Character Sets and Collations in MySQL 9.1.3. Specifying Character Sets and Collations 9.1.4. Connection Character Sets and Collations 9.1.5. Collation Issues 9.1.6. String Repertoire 9.1.7. Operations Affected by Character Set Support 9.1.8. Unicode Support 9.1.9. UTF-8 for Metadata 9.1.10. Column Character Set Conversion 9.1.11. Character Sets and Collations That MySQL Supports MySQL includes character set support th
» http://dev.mysql.com/doc/refman/5.0/en/charset.html
11. MySQL :: MySQL 5.1 with Maria Reference Manual :: 9.1 Character Set Support
9.1. Character Set Support [ +/- ] 9.1.1. Character Sets and Collations in General 9.1.2. Character Sets and Collations in MySQL 9.1.3. Specifying Character Sets and Collations 9.1.4. Connection Character Sets and Collations 9.1.5. Collation Issues 9.1.6. String Repertoire 9.1.7. Operations Affected by Character Set Support 9.1.8. Unicode Support 9.1.9. UTF-8 for Metadata 9.1.10. Column Character Set Conversion 9.1.11. Character Sets and Collations That MySQL Supports MySQL includes character set support th
» http://dev.mysql.com/doc/refman/5.1-maria/en/charset.html
12. MySQL :: MySQL 6.0 Reference Manual :: 9.1 Character Set Support
9.1. Character Set Support [ +/- ] 9.1.1. Character Sets and Collations in General 9.1.2. Character Sets and Collations in MySQL 9.1.3. Specifying Character Sets and Collations 9.1.4. Connection Character Sets and Collations 9.1.5. Collation Issues 9.1.6. String Repertoire 9.1.7. Operations Affected by Character Set Support 9.1.8. Unicode Support 9.1.9. Upgrading from Previous to Current Unicode Support 9.1.10. UTF-8 for Metadata 9.1.11. Column Character Set Conversion 9.1.12. Character Sets and Collations
» http://dev.mysql.com/doc/refman/6.0/en/charset.html
9.1.5.5. Collations Must Be for the Right Character Set Each character set has one or more collations, but each collation is associated with one and only one character set. Therefore, the following statement causes an error message because the latin2_bin collation is not legal with the latin1 character set: mysql> SELECT _latin1 'x' COLLATE latin2_bin; ERROR 1253 (42000): COLLATION 'latin2_bin' is not valid for CHARACTER SET 'latin1' In some cases, expressions that worked before MySQL 4.1 fail in early vers
» http://dev.mysql.com/doc/refman/4.1/en/charset-collation-charset.html
14. MySQL :: MySQL 3.23, 4.0, 4.1 Reference Manual :: 9.1 Character Set Support
9.1. Character Set Support [ +/- ] 9.1.1. Character Sets and Collations in General 9.1.2. Character Sets and Collations in MySQL 9.1.3. Specifying Character Sets and Collations 9.1.4. Connection Character Sets and Collations 9.1.5. Collation Issues 9.1.6. Operations Affected by Character Set Support 9.1.7. Unicode Support 9.1.8. UTF-8 for Metadata 9.1.9. Upgrading Character Sets from MySQL 4.0 9.1.10. Character Sets and Collations That MySQL Supports Improved support for character set handling was added to
» http://dev.mysql.com/doc/refman/4.1/en/charset.html
| 1 to 14 of 14 |