I had a need to store an encrypted bytestring, and CharField doesn't work. But BinaryField uses LONGBLOB by default (at least on MySQL). Doesn't it make more sense to have a BinaryField equivalent of CharField, and use LONGBLOB for something analogous to TextField? As far as I can tell, the MySQL documentation definitely considers LONGBLOB/BLOB analogous to TEXT. Not sure the best way to approach an improvement, though; add a BytestringField? Would this be best served as a third-party package, or should it be part of Django proper?