The change has been merged into master, is there any chance it can be
backported to 2.2? It does afterall correct a regression that could lead to
data loss in a hard to detect manner ;P
If not then our choices are limited to:
1) Stay on 1.11 until 3.2. Not really feasible as our deps have started
I'd like to revive this discussion and try to come to a consensus as it's
something I find myself wishing for (for Postgres in particular).
My suggestion, after reading through everything:
Give CharField a default max_length that is consistent across all vendors.
It doesn't really matter what
