Florian: I don't think waiting for migrations in the Django core is totally necessary to fix a bug like this (or others that might be similar). With proper documentation in the release/upgrade notes, I think it's completely reasonable to expect someone working with Django to be able to run a manual SQL query to alter those columns.
If this is a core philosophy not to ask users to run manual queries on updates, is starting with a patch to enforce limits here a good thing? Thanks, -greg On Tuesday, June 19, 2012 9:12:47 AM UTC-5, Florian Apolloner wrote: > > Hi Greg, > > Django itself can't change that currently since there is no support for > schema alteration in Core. Once we get that we can tackle issues like that > and increase to a sensible limit. (both name and codename might cause > problems…). > > Cheers, > Florian > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/OygzSFWV74wJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
