I am not sure if this is a bug, or possibly configuration issue.
I am seeing errors when the users are inserting records into POSTS that have an apostrophe in them, ex, the work "can't" would fail. In the logs, this is what I see I am seeing <92> replacing an apostrophe, and then seeing an incorrect string value below. Is there a configuration in php, or mysql that I don't have correct? or is this a bug?
INSERT INTO
ubbt_POSTS
(POST_PARENT_ID, TOPIC_ID, POST_IS_TOPIC, POST_POSTED_TIME, POST_POSTER_IP, POST_SUBJECT, POST_BODY, POST_DEFAULT_BODY, POST_IS_APPROVED, POST_ICON, POST_HAS_POLL, POST_HAS_FILE, POST_MARKUP_TYPE, USER_ID, POST_PARENT_USER_ID, POST_ADD_SIGNATURE, POST_LAST_EDITED_TIME, POST_POSTER_NAME, POST_MD5)
VALUES
(153023, 17905, 0, 1591546837, '208.90.218.178', 'Posts title', 'as I can<92>t talk about this it ', 'as I can<92>t talk about this it', 1, 'book.gif', '0', '0', 'none', 8, 104, 1, 0, 'mrb', '')
- Incorrect string value: '\x92t tal...' for column 'POST_BODY' at row 1
Doing some looking around, it may have to do with the character set. Could someone check to see if I need to change the character_set_database to utf8mb4?
Database changed
mysql> SHOW VARIABLES
-> WHERE Variable_name LIKE 'character\_set\_%'
-> OR Variable_name LIKE 'collation%';
+--------------------------+--------------------+
| Variable_name | Value |
+--------------------------+--------------------+
| character_set_client | utf8mb4 |
| character_set_connection | utf8mb4 |
| character_set_database | utf8 |
| character_set_filesystem | binary |
| character_set_results | utf8mb4 |
| character_set_server | utf8mb4 |
| character_set_system | utf8 |
| collation_connection | utf8mb4_general_ci |
| collation_database | utf8_general_ci |
| collation_server | utf8mb4_general_ci |
+--------------------------+--------------------+
10 rows in set (0.01 sec)
