Whenever the database is migrated, rails adds those values. It's a big pain to undo them every time, so when I am not adding features regularly anymore, I'll change it to the way it was.
Whenever the database is migrated, rails adds those values. It's a big pain to undo them every time, so when I am not adding features regularly anymore, I'll change it to the way it was.
The change from 255 to 191 is because we're using utf8mb4. MySQL reserves a certain amount of bytes, but the limit is given in characters, where 191 chars * 4 bytes <= 255 chars * 3 bytes.
The 65536 limit on a TEXT confuses me though, it shouldn't do that.
The change from 255 to 191 is because we're using `utf8mb4`. MySQL reserves a certain amount of bytes, but the limit is given in characters, where **`191 chars`**` * 4 bytes <= 255 chars * 3 bytes`.
The 65536 limit on a `TEXT` confuses me though, it shouldn't do that.
This repo is archived. You cannot comment on pull requests.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Might I ask why it's shortening the thread character limit to 65536 and the title character limit to 191?
Whenever the database is migrated, rails adds those values. It's a big pain to undo them every time, so when I am not adding features regularly anymore, I'll change it to the way it was.
The change from 255 to 191 is because we're using
utf8mb4. MySQL reserves a certain amount of bytes, but the limit is given in characters, where191 chars* 4 bytes <= 255 chars * 3 bytes.The 65536 limit on a
TEXTconfuses me though, it shouldn't do that.