tickets: 8298
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8298 | 2008-08-13 22:47:21 | 2011-09-28 16:12:17 | 2022-03-06 03:41:52.966223 | Accepted | closed | Uncategorized | dev | fixed | Missing to_python methods causing issues with serialization | 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. | nobody | andrewbadr | 0 | 0 | 0 | 0 | 0 | 0 |