#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
Resolution: |
Keywords:
Stage: Accepted |
Has_patch: 1
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------------------------+----
Changes (by Richard Davies <[EMAIL PROTECTED]>):
* needs_better_patch: 1 => 0
Comment:
OK, I've validated this against the full test suite on both sqlite3 and
postgresql_psycopg2. It is ready to check in.
The patches:
- create-always-inserts.v3.diff is the actual fix to the ticket
- authors.diff adds me to the authors list
- I have 3 sets of tests which could reasonably added to the test suite:
8669_tests.v2.diff (above), 8739_save_force_insert.v2.diff (on ticket
#8739), 8740_save_force_update.v2.diff (on ticket #8740). In all cases, be
careful to create _init_.py files, which the patches don't seem to do for
me.
--
Ticket URL: <http://code.djangoproject.com/ticket/8669#comment:8>
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
-~----------~----~----~----~------~----~------~--~---
