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?
-- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/16540fe7-ea21-4021-a47e-a2ecff7caded%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
