On 19/06/12 15:25, Stephan Jaensch wrote: > Hi Florian, > > Am 19.06.2012 um 16:12 schrieb Florian Apolloner: > >> 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…). > > How is this a factor if the limit exists only at the database level > and is not enforced or considered in Django code? Django code > already creates values that are too long for the fields. You would > just eliminate this bug on new installations. In the case of > usernames and email addresses, the limit was enforced in Django > code, so increasing the field length could break existing > installations since we can't do automatic schema migrations. But in > this case, things already break since Django does not care about > the field length.
I agree, this is one of the few cases where it's possible to get away without a schema migration, as the behaviour if we made this change would be exactly the same on old installations and it would be fixed on newer ones. Of course, this just leads to a higher limit after which you have values which are too long, but if your class names are getting over 200 characters long I suggest you have other issues. 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.
