Commit
utf8mb4
.
cf. GH-286
- Loading branch information
There are no files selected for viewing
2 comments
on commit 3c3380d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, for some reason I didn't consider much about the case where you make a fresh install with DATABASE_ENCODING=utf8mb4 because I had been focused on fixing existing installation. There was an assumption that the default database encoding which would affect those of the tables in it was utf8.
With the latest fix I committed a new database will be created in utf8 even if DATABASE_ENCODING is set to utf8mb4 so you can set up Huginn with DATABASE_ENCODING=utf8mb4 from the beginning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, cool! :)
Will this cause people to have the
Specified key was too long; max key length is 1000 bytes
error that showed up in #414 (comment) ?