On 19/06/12 16:13, Greg Aker wrote: > 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?
It's messy to ask people to manually run SQL queries to change this stuff in general - we'd have to provide four or five different queries, and the operation isn't even possible on SQLite (you'd have to make a new table with the right schema and copy things over). I'm working studiously on getting schema migration stuff in, it'll just take a release or two till it's ready. As for the interim solution, I replied to Stephan's post about that - I think just increasing max_length will work well enough for now in this case, as it's one of the few situations where the schema is slightly decoupled from the models. Andrew -- You received this message because you are subscribed to the Google Groups "Django developers" group. 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.
