Since the landing was already very popular in the way of landing, the relevance should also be considered in database design. General storage open_id, icons, nicknames is enough. The nickname should be special attention, otherwise it might be like this:
mysql:1366 incorrect string value bar bar ...
This is because the nickname uses special characters, such as the Unicode emoji extension area. MySQL UTF8 default is not stored, the number of bits is insufficient. Reference: attached link 1
The corresponding field should be modified to UTF8MB4, and the parameters of the stored procedure should also be modified (link 2):
CREATE PROCEDURE ' emoji ' (textvarchar() CHARSET utf8mb4)BEGIN SELECTtext; END
To test this problem can be used:
Select unhex ('f09f8d83')
Or
INSERT TB ('textVALUES' (Unhex ('f09f8d83'))
Link 1:http://www.cnblogs.com/lampbrotherit/p/5794742.html
Link 2:https://stackoverflow.com/questions/17650662/creating-a-stored-procedure-with-utf8-strings
MySQL with emoji and special characters