#13921: Inconsistent get_internal_type on official models' fields
---------------------------------------------------+------------------------
Reporter: mitar | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by mitar):
As I explained, it is useful to be able to automatically define fields
over which to search over. `get_internal_type` is probably meant just for
such cases where you need a way to inspect things dynamically. Having
inconsistencies there defeats its purpose.
I do not believe this is much of code shuffling, just changing few lines
(return values of `get_internal_type`). And as things are currently I do
not believe there is a need for a deprecation timeline, as this return
values are not quite predictable so any code using `get_internal_type`
have to already be robust to handle different cases.
--
Ticket URL: <http://code.djangoproject.com/ticket/13921#comment:2>
Django <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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
