id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 4048,mysql introspection doesn't handle CHAR(n) fields,Bill Fenner ,Adrian Holovaty,"I have a legacy table that has columns like {{{ CREATE TABLE `foo_info` ( `foo_tag` int(11) NOT NULL auto_increment, `record_type` char(8) default NULL, `name_prefix` char(10) default NULL, `first_name` char(20) default NULL, ... }}} note: CHAR, not VARCHAR. ""python manage.py inspectdb"" turns these into TextFields since it doesn't know any better. They work much better as CharFields; the attached diff makes that happen. ",,closed,"Database layer (models, ORM)",0.96,,fixed,mysql inspectdb,,Ready for checkin,1,0,0,0,0,0