tickets: 8669
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8669 | 2008-08-29 08:15:02 | 2011-09-28 16:12:17 | 2022-03-06 03:42:51.725361 | Accepted | closed | Database layer (models, ORM) | dev | fixed | All remaining create() methods also force an insert (continuation of r8670) | #8419 / [8670] forced an SQL insert in the main create() and get_or_create() methods, preventing data loss from overwriting existing data - thanks Malcolm! All other get_or_create() methods end up calling back to the main get_or_create(). However, there are a few extra create() methods which don't call back to the main create() - this patch ensures that those also force an insert, so cannot overwrite existing data. Extra methods found via "find django -name '*.py' | xargs grep -F 'def create('" and "find django -name '*.py' | xargs grep -F 'def get_or_create('" | nobody | Richard Davies <richard.davies@elastichosts.com> | 0 | 1 | 0 | 0 | 0 | 0 |