#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 Bill Fenner <[EMAIL PROTECTED]>):
I missed that the STRING -> TextField mapping was done explicitly. I
attached a new patch that changes the existing mapping instead of adding a
new one at the end.
CharField is a much better match for STRING than TextField is. Neither
one will exactly recreate the original schema with "python manage.py sql",
but STRINGs are much closer to VAR_STRINGs than they are to BLOBs.
--
Ticket URL: <http://code.djangoproject.com/ticket/4048#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
