On Mar 12, 3:23 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > A change to fix this (make the length longer) will be committed after > 0.96. I'm intentionally not committing it beforehand because it is a > backwards incompatible change in the sense that every database using > such a field will need to alter the respective column in the database > (there is now the possibility of submitting a string longer than 100 > chars, so it had better fit in the database column).
That makes sense. I might have to leave my working copy modified for now. Unfortunately adding a maxlength to an ImageField breaks admin, but I need to be able to store > 100 char URLs. Thanks Malcolm. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
