#8548: Lengthy verbose_name results in fatal mysql 'warning' error during
syncdb.
-------------------------------------+-------------------------------------
Reporter: samt@… | Owner: marcelor
Type: Bug | Status: assigned
Milestone: | Component: Core (Management
Version: | commands)
1.0-beta-1 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by anonymous):
* ui_ux: => 0
Comment:
The resolution to ticket #4748 is nonsensical. How would *increasing* the
length of the field break backwards compatibility? Any working application
in production up to this point logically must have all auth_permissions
character lengths of below 50 right now, making it a decidedly backwards
compatible change. If those apps that are in production add an auth
permission that has a length of greater than 50 in the future, then yes,
they would have to manually change it in the DB, but that is preferable to
making EVERY user with this issue manually change their DB.
This seems to me to be a case where a developer is hiding behind a
technicality to push off a change that fixes broken functionality.
--
Ticket URL: <https://code.djangoproject.com/ticket/8548#comment:16>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en.
