RDS MYSQL Database Emoji Configuration - mysql

I am working on emoji's to work with mysql database.
First thing my application uses RDS with version "5.6.22". I used the following link to handle emoji's for RDS mysql DB:
http:/aprogrammers.blogspot.in/2014/12/utf8mb4-character-set-in-amazon-rds.html
As link say's we have to update character set to "utf8mb4" so I did the changes accordingly.
Please find attached image having "Character Set" related variables settings for RDS (RDS-config.JPG).
Still after doing correct configuration, I am getting error saying as follow:
"Incorrect string value: '\xF0\x9D\x8C\x86' for column 'column_name' at row 1 ".
Second thing is that when I am working with local mysql DB which has version "5.7.15". I did that same changes with Character set variables for "utf8mb4". For details please check attached image (Local-config.JPG).
Now if I connect to local DB, emoji works fine.
I can anyone help me out with this issue.
Thanks in advance.
Harshvardhan Pawar
RDS Config details:
enter image description here
Local Config details:
enter image description here

I had very similar issue. The problem was that I set utf8mb4 for Parameter Group which was not selected as default group of my RDS instance.

Related

How to set UTF8 encoding for ClearDB (MySQL) on Heroku

Database I have on heroku doesn't support special characters so I want to set utf8 encoding. When I was working on local version I simply changed config files but I wonder how I can achieve this using Heroku's DB.
This added to connection url doesn't help:
?useUnicode=true&characterEncoding=UTF-8
I resolved this problem when I set this ?useUnicode=true&characterEncoding=UTF-8 into "Config Vars" on site heroku.com in section "settings" after question mark. Look up at image description here http://images.vfl.ru/ii/1588540106/e4c9cfa2/30400062.jpg
Switch from the ClearDB heroku add-on JawsDB MySQL solve my problem.

mysql 5.5 command line client error 1366 HY000 :incorrect string value:'\xD3\xE3\xC0

enter image description hereI want to insert many languages into my mysql database using command line client but the error still prompt out after i've try to change my collation of database, table into utf8_general_ci and utf8_unicode_ci. How to solve it?
I appreciate who can help this working.
it is about one of the row in your database you should make sure your database or table is empty then do such things

Type not supported - The JSON data is not available before MySQL 5.7.8

I am running local MySQL instance version of 5.7.23 in Ubuntu-18-04. The DB is already having some tables having JSON fields to store JSON data. They working fine with insert, update and delete operations.
The issue comes when try to modify an existing table to have a new field to store JSON data. MySQL-Workbench is giving an error saying
Type not supported
The JSON data is not available before MySQL 5.7.8.
In order to use it, first set the version for your model to 5.7.8 or
higher
Following screen shots shows my local environment information.
The error:
MySQL server info:
MySQL Workbench info:
I was able to figure the issue. The default version set for Modeling MySQL was set as 5.6.30. Changed it to 5.7.8 and works the table schema modification.
Go to Edit -> Preferences... in MySQL Workbench
Refer the below screens:
Before:
After:
Preference doesn't work for me. I use osx with workbench version 8.0.11.
Model in top bar menu -> Model Options -> MySQL then change the version as Shantha's answer works for me.
Previous version of MySQLWorkbench (6.3.10) has better error message for this...

MySQL query action output language

I'm hoping this is a simple question. I recently installed MySQL Workbench, and thought everything was going fine, until I noticed the output of messages at the bottom. They're in a foreign language. See attached screenshot. I tried the same queries in phpMyAdmin and get similar results.
Server connection collation: utf8mb4_general_ci (I tried to change to utf8_general_ci but it won't let me)
Any help is greatly appreciated.
Try changing your my.ini file to the following:
lc-messages=en_US
or run the command prompt and in the mysql prompt do:
SET lc_messages = 'en_US';
Check the following reference

Unable to initialize provider. Missing or incorrect schema

I have upgraded my server machine to use MySQL Connector 6.3.4 and in our website we also added Membership role provider.
When I run the website I am getting this error.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Unable to initialize provider. Missing or incorrect schema.
My sql server is version 5.0.90 community-net.
Is there any setting which have to be changes on server side while upgrading connector
This is tag in my web.config file.
Since when I run the website on local machine it will run successfully, but on server I am not able to run it and getting above error.
There is no mistake in connection string
What are server side setting which we to do while upgrading the connector....
thanks
I myself running into the same problem. I m using Mysql connector 6.3.0.0
So far I came across following suggestions when seaching on net:
1) Add "MySql.Data.dll" & "MySql.Web.dll" into your application "bin" folder.
2) Add reference to above to dlls in your application .
3) Add autogenerateschema="true" in your web.config file for required sections.
4) Check your Mysql connector version - make sure that the one that is in your bin folder is mentioned in your web.config file.
5) Check your connection string - make sure it is correct and connected successfully.
6) Check mysql membership related table structure.
7) Check schema version in "my_aspnet_schemaversion" table (e.g since you have upgraded to newer version I insist you should check this).
8) If the problem is on remote machine (e.g Production Server) you may wan to check this : http://www.reggieburnett.com/referencing-connectornet-on-a-remote-machine
I m sure you may gone through this list but I would like you to check schema version in "my_aspnet_schemaversion" table (e.g compare "version" field value of your local and remote table) since your upgrading to newer version.
BTW: I have checked this list for my problem but it did not help. I hope it may be of some help to you.
Edit:
Hi,
We are able to fix this error by following:
1) Deleted the tables for memberships in the db and had the mysql membership provider regenerate them
2) than set the Aministration.config file to trust the Mysql Membership Provider (e.g related to IIS admin)
Regards,
Gaurav
I had this same problem after checking all the things in Gaurav's post. It ended up being that the user account I was using in my connection string did not have necessary permissions to alter the db schema (I had autogenerateschema set to true). Once I changed my connection string to a user with more privileges (I used the 'root' user) then it updated the schema, and I changed the connection string back to the original user.
Always make sure that the Datasource is set to the real ip address and not localhost and check the passwords and usernames too. I am working with these clients and their ip address keeps changing and every time they do that, I get the same error
I know this is an old thread but maybe this will help someone. I was having this issue and realized that I was editing the wrong machine.config
At first I was editing on under C:\Windows\Microsoft.NET\Framework64....
Once I found the one for my .NET version under C:\Windows\Microsoft.NET\Framework.... and edited the correct spots, it worked fine following the instructions on MySQL's site.