#14518: Field.to_python not called on foreign key IDs
---------------------------------------------------+------------------------
Reporter: wolever | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by russellm):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* component: Uncategorized => Database layer (models, ORM)
* needs_tests: => 0
* needs_docs: => 0
Comment:
Accepting, because it's clearly an inconsistency.
However, I have a sneaking suspicion that this won't be easy to fix
without breaking backwards compatibility. For historical reasons, it's
possible to instantiate an object with string values, and those values
aren't converted into field-appropriate values (integers, etc) until the
object is saved to the database. This is an artefact of early-days Django
form processing.
--
Ticket URL: <http://code.djangoproject.com/ticket/14518#comment:1>
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 [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.
