1👍
As the docs state here, 65.535 are actually bytes, which leads to a maximum of 21.844 characters if using UTF-8.
A variable-length string. M represents the maximum column length in
characters. The range of M is 0 to 65,535. The effective maximum
length of a VARCHAR is subject to the maximum row size (65,535 bytes,
which is shared among all columns) and the character set used. For
example, utf8 characters can require up to three bytes per character,
so a VARCHAR column that uses the utf8 character set can be declared
to be a maximum of 21,844 characters.
Since the max_length of a CharField in a Django model specifies the length in characters rather than in bytes, I assume this is what causes the error.
0👍
Make the table MyISAM or InnoDB. Either will quickly cache your string, thereby making respond as if it were “in-memory”.
As for the confusing error message — a VARCHAR that needs more than 64K bytes is silently turned into MEDIUMTEXT.
If your string can be broken into multiple pieces, you could have multiple rows. (Have a second column with a row number of some kind.)
- Django – Greedy AND Query on ManyToMany
- How can I query models in Django with attributes in a JSONField?
- Unable to upload image using shell in django
- Django: admin login with parameter