#4048: mysql introspection doesn't handle CHAR(n) fields
----------------------------------------------+-----------------------------
Reporter: Bill Fenner <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component: Database
wrapper
Version: 0.96 | Resolution:
Keywords: mysql inspectdb | Stage: Ready
for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------------------+-----------------------------
Comment (by mtredinnick):
A bit subjective, this one, but I'm inclined to agree that !CharField will
be more appropriate. The backwards-incompat change is unlikely to bite
anybody badly, either.
In future, please make patches from the route of the source tree so that
we can see which file is patched (in this case, it's easy enough to work
it out, but not always).
--
Ticket URL: <http://code.djangoproject.com/ticket/4048#comment:3>
Django Code <http://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
-~----------~----~----~----~------~----~------~--~---
