You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When creating a new Book it happened to me that a document title included an emoji which caused a database error: Mysql2::Error: Incorrect string value: ...
The error is caused because the database column display_fields in the database table query_doc_pairs uses the deprecated (I think at least it's deprecated) charset utf8mb3.
Changing the charset in the database table resolved the issue for me:
ALTER TABLE query_doc_pairs MODIFY document_fields mediumtext CHARACTER SET utf8mb4;
Describe the solution you'd like
Change the charset for the database table query_doc_pairs from utf8mb3 to utf8mb4.
The changed line should look like this: create_table "query_doc_pairs", charset: "utf8mb4", collation: "utf8mb4_unicode_ci", force: :cascade do |t|
From my perspective it makes sense to look at the rest of the database tables and columns as well and see if this makes sense for more than just the one table.
Describe alternatives you've considered
No alternatives considered.
Additional context
No screenshots to share.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When creating a new Book it happened to me that a document title included an emoji which caused a database error:
Mysql2::Error: Incorrect string value: ...
The error is caused because the database column
display_fields
in the database tablequery_doc_pairs
uses the deprecated (I think at least it's deprecated) charsetutf8mb3
.Changing the charset in the database table resolved the issue for me:
ALTER TABLE query_doc_pairs MODIFY document_fields mediumtext CHARACTER SET utf8mb4;
Describe the solution you'd like
Change the charset for the database table
query_doc_pairs
fromutf8mb3
toutf8mb4
.As of now this change would need to happen in here: https://github.com/o19s/quepid/blob/main/db/schema.rb#L183
The changed line should look like this:
create_table "query_doc_pairs", charset: "utf8mb4", collation: "utf8mb4_unicode_ci", force: :cascade do |t|
From my perspective it makes sense to look at the rest of the database tables and columns as well and see if this makes sense for more than just the one table.
Describe alternatives you've considered
No alternatives considered.
Additional context
No screenshots to share.
The text was updated successfully, but these errors were encountered: