Hi all, On Tuesday, June 19, 2012 5:12:47 PM UTC+3, 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 >
I have suggested, on the bug itself, a partial solution that requires no database schema change (elide the "name" field if it's too long, as it is only used for display anyway). The "codename" field will then stay problematic, but the limitation there is much less severe. Have fun, Shai. -- 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/-/ly9RVtN53MsJ. 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.
