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 13921,Inconsistent get_internal_type on official models' fields,Mitar,nobody,"I think there is a small inconsistency on when does `get_internal_type` return base type and when it defines as a new type in official models' fields. I wanted to make a dynamic list of searchable fields (`search_fields`) in admin by inspecting all defined fields in a model and adding all those which have `get_internal_type` defined as `CharField` or `TextField` (and ignoring those which define choices, but this is not important here). This works great on `EmailField` and `URLField` among official models' fields. But there is a strange situation with `SlugField` and `CommaSeparatedIntegerField`. The first defines new type (named `SlugField`) which is OK by me if we say that it changes semantics somewhat. But then why `CommaSeparatedIntegerField` does not define new type but leave it as `CharField` where this field is definitely something special. I would suggest `SlugField` returns `CharField` and that `CommaSeparatedIntegerField` returns `CommaSeparatedIntegerField`. Or to do at least just the later.",,closed,"Database layer (models, ORM)",1.2,,wontfix,,mmitar@…,Unreviewed,0,0,0,0,0,0