#3729: For integer field inside Model.save() is provided string value when
'choices' option is used
-------------------------------------+--------------------------------------
Reporter: EntropyHacker | Owner: nobody
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: choices, integerfield | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------+--------------------------------------
Changes (by rcoup):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
This isn't technically a problem in the models (well, I can't reproduce it
using your code). They don't currently do any validation (including
limiting to choices or even checking whether things are integers). It's a
big work-in-progress to get model validation happening.
However, if data comes back from a `newforms.ChoiceField` it's always a
string, not whatever type is in the `choices` list.
--
Ticket URL: <http://code.djangoproject.com/ticket/3729#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
