#5784: Include field name that causes validation error in CharField.to_python
---------------------------------------------+------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Component: Database
wrapper
Version: SVN | Resolution: wontfix
Keywords: initial_data syncdb CharField | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 1
---------------------------------------------+------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
The error message altered by this patch isn't just a
serialization/fixtures error - it is used by other subsystems.
In addition, there could be thousands of Model instances in a fixture,
each of which will have a value for 'field'. Saying "Model.field cannot be
none" won't help you find which Model.field instance in your fixture is
the cause of the error. #6397 is a better proposal for improving error
messages (although the implementation suggested there is not feasible).
On an administrative note, a complete patch should be generated against
the root of the source tree - there are many __init__.py files in Django,
and the patch you provided doesn't provide any context to say which file
has been modified. A good patch will also include a test that validates
the behaviour that has been modified.
--
Ticket URL: <http://code.djangoproject.com/ticket/5784#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
