Struggling with MySQL character set, collation












2















I am facing problems with inserting Spanish characters from my application.



When I am inserting on the DB the characters are inserting properly, but when I am trying passing the same data in from the application, the data stored in the table isn't correct.



For example, when I insert directly on DB server:



CREATE TABLE  prod_inns(`prod_name` varchar(100) COLLATE latin1_bin DEFAULT NULL)

insert into prod_inns values(Otoño);


I see this:



select * from prod_inns ;

+-------------+
| prod_name |
+-------------+
| Otoño |
+-------------+

delete FROM prod_inns ;


However, when I insert the same value from the application form, I see this instead:



select * from prod_inns ;

+-------------+
| prod_name |
+-------------+
| Otoño |
+-------------+


Here are my MySQL settings:



MySQL>  show global variables like 'char%';
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+

MySQL> show global variables like 'coll%';
+----------------------+-------------------+
| Variable_name | Value |
+----------------------+-------------------+
| collation_connection | latin1_swedish_ci |
| collation_database | latin1_swedish_ci |
| collation_server | latin1_swedish_ci |
+----------------------+-------------------+
3 rows in set (0.00 sec)


What's wrong with my settings? What should I do to store the data and read the data properly?



Note: I am using mysql-5.7.19










share|improve this question
















bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • IN additional to the answers below - just checking, you're trying to get Spanish characters correct, and you're using latin1_swedish_ci as your default collation? Wanted to be sure that was deliberate - if so, fine.

    – RDFozz
    Oct 16 '17 at 18:03











  • yes i am trying to get spanish charecters and i am using latin1_swedish_ci collation .

    – Jock helson
    Oct 18 '17 at 7:49
















2















I am facing problems with inserting Spanish characters from my application.



When I am inserting on the DB the characters are inserting properly, but when I am trying passing the same data in from the application, the data stored in the table isn't correct.



For example, when I insert directly on DB server:



CREATE TABLE  prod_inns(`prod_name` varchar(100) COLLATE latin1_bin DEFAULT NULL)

insert into prod_inns values(Otoño);


I see this:



select * from prod_inns ;

+-------------+
| prod_name |
+-------------+
| Otoño |
+-------------+

delete FROM prod_inns ;


However, when I insert the same value from the application form, I see this instead:



select * from prod_inns ;

+-------------+
| prod_name |
+-------------+
| Otoño |
+-------------+


Here are my MySQL settings:



MySQL>  show global variables like 'char%';
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+

MySQL> show global variables like 'coll%';
+----------------------+-------------------+
| Variable_name | Value |
+----------------------+-------------------+
| collation_connection | latin1_swedish_ci |
| collation_database | latin1_swedish_ci |
| collation_server | latin1_swedish_ci |
+----------------------+-------------------+
3 rows in set (0.00 sec)


What's wrong with my settings? What should I do to store the data and read the data properly?



Note: I am using mysql-5.7.19










share|improve this question
















bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • IN additional to the answers below - just checking, you're trying to get Spanish characters correct, and you're using latin1_swedish_ci as your default collation? Wanted to be sure that was deliberate - if so, fine.

    – RDFozz
    Oct 16 '17 at 18:03











  • yes i am trying to get spanish charecters and i am using latin1_swedish_ci collation .

    – Jock helson
    Oct 18 '17 at 7:49














2












2








2


0






I am facing problems with inserting Spanish characters from my application.



When I am inserting on the DB the characters are inserting properly, but when I am trying passing the same data in from the application, the data stored in the table isn't correct.



For example, when I insert directly on DB server:



CREATE TABLE  prod_inns(`prod_name` varchar(100) COLLATE latin1_bin DEFAULT NULL)

insert into prod_inns values(Otoño);


I see this:



select * from prod_inns ;

+-------------+
| prod_name |
+-------------+
| Otoño |
+-------------+

delete FROM prod_inns ;


However, when I insert the same value from the application form, I see this instead:



select * from prod_inns ;

+-------------+
| prod_name |
+-------------+
| Otoño |
+-------------+


Here are my MySQL settings:



MySQL>  show global variables like 'char%';
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+

MySQL> show global variables like 'coll%';
+----------------------+-------------------+
| Variable_name | Value |
+----------------------+-------------------+
| collation_connection | latin1_swedish_ci |
| collation_database | latin1_swedish_ci |
| collation_server | latin1_swedish_ci |
+----------------------+-------------------+
3 rows in set (0.00 sec)


What's wrong with my settings? What should I do to store the data and read the data properly?



Note: I am using mysql-5.7.19










share|improve this question
















I am facing problems with inserting Spanish characters from my application.



When I am inserting on the DB the characters are inserting properly, but when I am trying passing the same data in from the application, the data stored in the table isn't correct.



For example, when I insert directly on DB server:



CREATE TABLE  prod_inns(`prod_name` varchar(100) COLLATE latin1_bin DEFAULT NULL)

insert into prod_inns values(Otoño);


I see this:



select * from prod_inns ;

+-------------+
| prod_name |
+-------------+
| Otoño |
+-------------+

delete FROM prod_inns ;


However, when I insert the same value from the application form, I see this instead:



select * from prod_inns ;

+-------------+
| prod_name |
+-------------+
| Otoño |
+-------------+


Here are my MySQL settings:



MySQL>  show global variables like 'char%';
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+

MySQL> show global variables like 'coll%';
+----------------------+-------------------+
| Variable_name | Value |
+----------------------+-------------------+
| collation_connection | latin1_swedish_ci |
| collation_database | latin1_swedish_ci |
| collation_server | latin1_swedish_ci |
+----------------------+-------------------+
3 rows in set (0.00 sec)


What's wrong with my settings? What should I do to store the data and read the data properly?



Note: I am using mysql-5.7.19







mysql linux






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 16 '17 at 17:58









RDFozz

9,82731430




9,82731430










asked Oct 16 '17 at 16:33









Jock helsonJock helson

111




111





bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • IN additional to the answers below - just checking, you're trying to get Spanish characters correct, and you're using latin1_swedish_ci as your default collation? Wanted to be sure that was deliberate - if so, fine.

    – RDFozz
    Oct 16 '17 at 18:03











  • yes i am trying to get spanish charecters and i am using latin1_swedish_ci collation .

    – Jock helson
    Oct 18 '17 at 7:49



















  • IN additional to the answers below - just checking, you're trying to get Spanish characters correct, and you're using latin1_swedish_ci as your default collation? Wanted to be sure that was deliberate - if so, fine.

    – RDFozz
    Oct 16 '17 at 18:03











  • yes i am trying to get spanish charecters and i am using latin1_swedish_ci collation .

    – Jock helson
    Oct 18 '17 at 7:49

















IN additional to the answers below - just checking, you're trying to get Spanish characters correct, and you're using latin1_swedish_ci as your default collation? Wanted to be sure that was deliberate - if so, fine.

– RDFozz
Oct 16 '17 at 18:03





IN additional to the answers below - just checking, you're trying to get Spanish characters correct, and you're using latin1_swedish_ci as your default collation? Wanted to be sure that was deliberate - if so, fine.

– RDFozz
Oct 16 '17 at 18:03













yes i am trying to get spanish charecters and i am using latin1_swedish_ci collation .

– Jock helson
Oct 18 '17 at 7:49





yes i am trying to get spanish charecters and i am using latin1_swedish_ci collation .

– Jock helson
Oct 18 '17 at 7:49










2 Answers
2






active

oldest

votes


















0














Don't use latin1, use utf8. You have "Mojibake" because the bytes in the client are utf8-encoded, yet you said they were latin1.



More on Mojibake and what to do about it: https://stackoverflow.com/questions/38363566/trouble-with-utf8-characters-what-i-see-is-not-what-i-stored






share|improve this answer
























  • I tried your sugesstion. I have altered the table column charecter set as utf8 but still there is no change in result . alter table prod_inns modify prod_name varchar(100) CHARSET utf8; result: select * from prod_inns ; Otoño

    – Jock helson
    Oct 16 '17 at 16:56













  • Yes, but it was inserted erroneously to begin with. Try doing the insert again! p.s. use backticks (`) to highlight actual code in comments!

    – Vérace
    Oct 16 '17 at 17:00













  • The 'correct' fix was to do a pair of ALTERs, hopping through VARBINARY. See here. (I don't want to think about how to fix it now that you have compounded the problems.

    – Rick James
    Oct 16 '17 at 17:04













  • i tried with backtick while inserting throwing ERROR 1054 (42S22): Unknown column 'Otoño' in 'field list' Tried with varbinary as well still same problem persisting.

    – Jock helson
    Oct 16 '17 at 17:10











  • @Jockhelson - you missed Vérace's point -- backtics are a formatting convention to get This Look instead of This Look in Comments (and in Q&A).

    – Rick James
    Oct 16 '17 at 17:24



















0














You need to alter your database character set and collation as per the instructions here:



i.e.



ALTER  DATABASE database_name
CHARACTER SET character_set_name
COLLATE collation_name


in your case, it should be



ALTER DATABASE my_database
CHARACTER SET utf8
COLLATE spanish_unicode_ci


(or spanish2 if you want Traditional - as per here)






share|improve this answer


























  • Those are only defaults for new tables. So these ALTERs will not have any effect.

    – Rick James
    Oct 16 '17 at 17:02











  • mysql> ALTER DATABASE ecomm CHARACTER SET utf8 COLLATE spanish_unicode_ci; ERROR 1273 (HY000): Unknown collation: 'spanish_unicode_ci' I recently upgraded mysql to 5.5 to 5.7 , it worked properly in my old mysql version.

    – Jock helson
    Oct 16 '17 at 17:04













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f188581%2fstruggling-with-mysql-character-set-collation%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Don't use latin1, use utf8. You have "Mojibake" because the bytes in the client are utf8-encoded, yet you said they were latin1.



More on Mojibake and what to do about it: https://stackoverflow.com/questions/38363566/trouble-with-utf8-characters-what-i-see-is-not-what-i-stored






share|improve this answer
























  • I tried your sugesstion. I have altered the table column charecter set as utf8 but still there is no change in result . alter table prod_inns modify prod_name varchar(100) CHARSET utf8; result: select * from prod_inns ; Otoño

    – Jock helson
    Oct 16 '17 at 16:56













  • Yes, but it was inserted erroneously to begin with. Try doing the insert again! p.s. use backticks (`) to highlight actual code in comments!

    – Vérace
    Oct 16 '17 at 17:00













  • The 'correct' fix was to do a pair of ALTERs, hopping through VARBINARY. See here. (I don't want to think about how to fix it now that you have compounded the problems.

    – Rick James
    Oct 16 '17 at 17:04













  • i tried with backtick while inserting throwing ERROR 1054 (42S22): Unknown column 'Otoño' in 'field list' Tried with varbinary as well still same problem persisting.

    – Jock helson
    Oct 16 '17 at 17:10











  • @Jockhelson - you missed Vérace's point -- backtics are a formatting convention to get This Look instead of This Look in Comments (and in Q&A).

    – Rick James
    Oct 16 '17 at 17:24
















0














Don't use latin1, use utf8. You have "Mojibake" because the bytes in the client are utf8-encoded, yet you said they were latin1.



More on Mojibake and what to do about it: https://stackoverflow.com/questions/38363566/trouble-with-utf8-characters-what-i-see-is-not-what-i-stored






share|improve this answer
























  • I tried your sugesstion. I have altered the table column charecter set as utf8 but still there is no change in result . alter table prod_inns modify prod_name varchar(100) CHARSET utf8; result: select * from prod_inns ; Otoño

    – Jock helson
    Oct 16 '17 at 16:56













  • Yes, but it was inserted erroneously to begin with. Try doing the insert again! p.s. use backticks (`) to highlight actual code in comments!

    – Vérace
    Oct 16 '17 at 17:00













  • The 'correct' fix was to do a pair of ALTERs, hopping through VARBINARY. See here. (I don't want to think about how to fix it now that you have compounded the problems.

    – Rick James
    Oct 16 '17 at 17:04













  • i tried with backtick while inserting throwing ERROR 1054 (42S22): Unknown column 'Otoño' in 'field list' Tried with varbinary as well still same problem persisting.

    – Jock helson
    Oct 16 '17 at 17:10











  • @Jockhelson - you missed Vérace's point -- backtics are a formatting convention to get This Look instead of This Look in Comments (and in Q&A).

    – Rick James
    Oct 16 '17 at 17:24














0












0








0







Don't use latin1, use utf8. You have "Mojibake" because the bytes in the client are utf8-encoded, yet you said they were latin1.



More on Mojibake and what to do about it: https://stackoverflow.com/questions/38363566/trouble-with-utf8-characters-what-i-see-is-not-what-i-stored






share|improve this answer













Don't use latin1, use utf8. You have "Mojibake" because the bytes in the client are utf8-encoded, yet you said they were latin1.



More on Mojibake and what to do about it: https://stackoverflow.com/questions/38363566/trouble-with-utf8-characters-what-i-see-is-not-what-i-stored







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 16 '17 at 16:47









Rick JamesRick James

41.6k22258




41.6k22258













  • I tried your sugesstion. I have altered the table column charecter set as utf8 but still there is no change in result . alter table prod_inns modify prod_name varchar(100) CHARSET utf8; result: select * from prod_inns ; Otoño

    – Jock helson
    Oct 16 '17 at 16:56













  • Yes, but it was inserted erroneously to begin with. Try doing the insert again! p.s. use backticks (`) to highlight actual code in comments!

    – Vérace
    Oct 16 '17 at 17:00













  • The 'correct' fix was to do a pair of ALTERs, hopping through VARBINARY. See here. (I don't want to think about how to fix it now that you have compounded the problems.

    – Rick James
    Oct 16 '17 at 17:04













  • i tried with backtick while inserting throwing ERROR 1054 (42S22): Unknown column 'Otoño' in 'field list' Tried with varbinary as well still same problem persisting.

    – Jock helson
    Oct 16 '17 at 17:10











  • @Jockhelson - you missed Vérace's point -- backtics are a formatting convention to get This Look instead of This Look in Comments (and in Q&A).

    – Rick James
    Oct 16 '17 at 17:24



















  • I tried your sugesstion. I have altered the table column charecter set as utf8 but still there is no change in result . alter table prod_inns modify prod_name varchar(100) CHARSET utf8; result: select * from prod_inns ; Otoño

    – Jock helson
    Oct 16 '17 at 16:56













  • Yes, but it was inserted erroneously to begin with. Try doing the insert again! p.s. use backticks (`) to highlight actual code in comments!

    – Vérace
    Oct 16 '17 at 17:00













  • The 'correct' fix was to do a pair of ALTERs, hopping through VARBINARY. See here. (I don't want to think about how to fix it now that you have compounded the problems.

    – Rick James
    Oct 16 '17 at 17:04













  • i tried with backtick while inserting throwing ERROR 1054 (42S22): Unknown column 'Otoño' in 'field list' Tried with varbinary as well still same problem persisting.

    – Jock helson
    Oct 16 '17 at 17:10











  • @Jockhelson - you missed Vérace's point -- backtics are a formatting convention to get This Look instead of This Look in Comments (and in Q&A).

    – Rick James
    Oct 16 '17 at 17:24

















I tried your sugesstion. I have altered the table column charecter set as utf8 but still there is no change in result . alter table prod_inns modify prod_name varchar(100) CHARSET utf8; result: select * from prod_inns ; Otoño

– Jock helson
Oct 16 '17 at 16:56







I tried your sugesstion. I have altered the table column charecter set as utf8 but still there is no change in result . alter table prod_inns modify prod_name varchar(100) CHARSET utf8; result: select * from prod_inns ; Otoño

– Jock helson
Oct 16 '17 at 16:56















Yes, but it was inserted erroneously to begin with. Try doing the insert again! p.s. use backticks (`) to highlight actual code in comments!

– Vérace
Oct 16 '17 at 17:00







Yes, but it was inserted erroneously to begin with. Try doing the insert again! p.s. use backticks (`) to highlight actual code in comments!

– Vérace
Oct 16 '17 at 17:00















The 'correct' fix was to do a pair of ALTERs, hopping through VARBINARY. See here. (I don't want to think about how to fix it now that you have compounded the problems.

– Rick James
Oct 16 '17 at 17:04







The 'correct' fix was to do a pair of ALTERs, hopping through VARBINARY. See here. (I don't want to think about how to fix it now that you have compounded the problems.

– Rick James
Oct 16 '17 at 17:04















i tried with backtick while inserting throwing ERROR 1054 (42S22): Unknown column 'Otoño' in 'field list' Tried with varbinary as well still same problem persisting.

– Jock helson
Oct 16 '17 at 17:10





i tried with backtick while inserting throwing ERROR 1054 (42S22): Unknown column 'Otoño' in 'field list' Tried with varbinary as well still same problem persisting.

– Jock helson
Oct 16 '17 at 17:10













@Jockhelson - you missed Vérace's point -- backtics are a formatting convention to get This Look instead of This Look in Comments (and in Q&A).

– Rick James
Oct 16 '17 at 17:24





@Jockhelson - you missed Vérace's point -- backtics are a formatting convention to get This Look instead of This Look in Comments (and in Q&A).

– Rick James
Oct 16 '17 at 17:24













0














You need to alter your database character set and collation as per the instructions here:



i.e.



ALTER  DATABASE database_name
CHARACTER SET character_set_name
COLLATE collation_name


in your case, it should be



ALTER DATABASE my_database
CHARACTER SET utf8
COLLATE spanish_unicode_ci


(or spanish2 if you want Traditional - as per here)






share|improve this answer


























  • Those are only defaults for new tables. So these ALTERs will not have any effect.

    – Rick James
    Oct 16 '17 at 17:02











  • mysql> ALTER DATABASE ecomm CHARACTER SET utf8 COLLATE spanish_unicode_ci; ERROR 1273 (HY000): Unknown collation: 'spanish_unicode_ci' I recently upgraded mysql to 5.5 to 5.7 , it worked properly in my old mysql version.

    – Jock helson
    Oct 16 '17 at 17:04


















0














You need to alter your database character set and collation as per the instructions here:



i.e.



ALTER  DATABASE database_name
CHARACTER SET character_set_name
COLLATE collation_name


in your case, it should be



ALTER DATABASE my_database
CHARACTER SET utf8
COLLATE spanish_unicode_ci


(or spanish2 if you want Traditional - as per here)






share|improve this answer


























  • Those are only defaults for new tables. So these ALTERs will not have any effect.

    – Rick James
    Oct 16 '17 at 17:02











  • mysql> ALTER DATABASE ecomm CHARACTER SET utf8 COLLATE spanish_unicode_ci; ERROR 1273 (HY000): Unknown collation: 'spanish_unicode_ci' I recently upgraded mysql to 5.5 to 5.7 , it worked properly in my old mysql version.

    – Jock helson
    Oct 16 '17 at 17:04
















0












0








0







You need to alter your database character set and collation as per the instructions here:



i.e.



ALTER  DATABASE database_name
CHARACTER SET character_set_name
COLLATE collation_name


in your case, it should be



ALTER DATABASE my_database
CHARACTER SET utf8
COLLATE spanish_unicode_ci


(or spanish2 if you want Traditional - as per here)






share|improve this answer















You need to alter your database character set and collation as per the instructions here:



i.e.



ALTER  DATABASE database_name
CHARACTER SET character_set_name
COLLATE collation_name


in your case, it should be



ALTER DATABASE my_database
CHARACTER SET utf8
COLLATE spanish_unicode_ci


(or spanish2 if you want Traditional - as per here)







share|improve this answer














share|improve this answer



share|improve this answer








edited Oct 16 '17 at 16:58

























answered Oct 16 '17 at 16:52









VéraceVérace

15.9k33349




15.9k33349













  • Those are only defaults for new tables. So these ALTERs will not have any effect.

    – Rick James
    Oct 16 '17 at 17:02











  • mysql> ALTER DATABASE ecomm CHARACTER SET utf8 COLLATE spanish_unicode_ci; ERROR 1273 (HY000): Unknown collation: 'spanish_unicode_ci' I recently upgraded mysql to 5.5 to 5.7 , it worked properly in my old mysql version.

    – Jock helson
    Oct 16 '17 at 17:04





















  • Those are only defaults for new tables. So these ALTERs will not have any effect.

    – Rick James
    Oct 16 '17 at 17:02











  • mysql> ALTER DATABASE ecomm CHARACTER SET utf8 COLLATE spanish_unicode_ci; ERROR 1273 (HY000): Unknown collation: 'spanish_unicode_ci' I recently upgraded mysql to 5.5 to 5.7 , it worked properly in my old mysql version.

    – Jock helson
    Oct 16 '17 at 17:04



















Those are only defaults for new tables. So these ALTERs will not have any effect.

– Rick James
Oct 16 '17 at 17:02





Those are only defaults for new tables. So these ALTERs will not have any effect.

– Rick James
Oct 16 '17 at 17:02













mysql> ALTER DATABASE ecomm CHARACTER SET utf8 COLLATE spanish_unicode_ci; ERROR 1273 (HY000): Unknown collation: 'spanish_unicode_ci' I recently upgraded mysql to 5.5 to 5.7 , it worked properly in my old mysql version.

– Jock helson
Oct 16 '17 at 17:04







mysql> ALTER DATABASE ecomm CHARACTER SET utf8 COLLATE spanish_unicode_ci; ERROR 1273 (HY000): Unknown collation: 'spanish_unicode_ci' I recently upgraded mysql to 5.5 to 5.7 , it worked properly in my old mysql version.

– Jock helson
Oct 16 '17 at 17:04




















draft saved

draft discarded




















































Thanks for contributing an answer to Database Administrators Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f188581%2fstruggling-with-mysql-character-set-collation%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

SQL Server 17 - Attemping to backup to remote NAS but Access is denied

Always On Availability groups resolving state after failover - Remote harden of transaction...

Restoring from pg_dump with foreign key constraints