Missing to_python methods causing issues with serialization
|Reported by:||andrewbadr||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Lack of to_python on IntegerField? is breaking our tests that read from XML fixtures.
From what I can tell, this how things are supposed to work: (1) an IntegerField is read in as unicode (from the XML fixture), (2) the row is saved to the database, and (3) field is an integer on the next read from db. However, on one model, we have a post-save signal handler that expects the field to be an integer. This handler throws an exception when it gets unicode, so our tests break.
Is accepting strings a part of the database interface definition? I'm guessing we'd hit this same problem if using a form.
Change History (4)
comment:1 Changed 8 years ago by mtredinnick
- milestone set to 1.0 maybe
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted