#8669: All remaining create() methods also force an insert (continuation of
r8670)
--------------------------------------------------------------+-------------
Reporter: Richard Davies <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Milestone:
1.0
Component: Database wrapper | Version:
SVN
Keywords: | Stage:
Unreviewed
Has_patch: 1 |
--------------------------------------------------------------+-------------
#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('"
--
Ticket URL: <http://code.djangoproject.com/ticket/8669>
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
-~----------~----~----~----~------~----~------~--~---
