#8548: Lengthy verbose_name results in fatal mysql 'warning' error during
syncdb.
-------------------------------------+-------------------------------------
Reporter: samt@… | Owner: marcelor
Type: Bug | Status: reopened
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 kmtracey):
* status: closed => reopened
* resolution: worksforme =>
Comment:
This is still re-creatable by me with a brand new MySQL database. I don't
imagine it would ever be re-creatable on sqlite: sqlite simply doesn't
enforce length restrictions. On MySQL whether it is a warning or an error
condition is determined by the strictness mode set. If MySQL is configured
to consider it just a warning situation, it's possible that the data will
just get truncated with a warning being printed at the console; Django
only turns MySQL warnings into exceptions when the DEBUG setting is True.
--
Ticket URL: <https://code.djangoproject.com/ticket/8548#comment:18>
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.
