#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:  1                                                 |  
-----------------------------------------------------------------------+----
Changes (by mtredinnick):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted

Comment:

 This patch (the second one, which is the one we're considering) causes a
 lot of failures in the test suite, even with SQLite. They need to be
 fixed. I'd also like some confirmation that the revised version runs
 against the full test suite on a database that supports transacations (one
 of the PostgreSQL backends or Oracle).

 Finally, given the scope of the change and the fact that it's already
 caused some problems, some tests to verify the new functionality would be
 a good idea.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8669#comment:4>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to