#16818: Regression introduced by r16739 -- `ManyRelatedManager.add()` doesn't
commit to database
-------------------------------------+-------------------------------------
     Reporter:  pressureman          |                    Owner:  kmtracey
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  SVN
  (models, ORM)                      |               Resolution:
     Severity:  Release blocker      |             Triage Stage:  Accepted
     Keywords:                       |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by kmtracey):

 I am confused by this test case:

 {{{
 #!python
 class TestManyToManyAddTransaction(TransactionTestCase):
     def test_manyrelated_add_commit(self):
         """test for 16818"""
         a = M2mA.objects.create()
         b = M2mB.objects.create(fld=10)
         a.others.add(b)
         transaction.rollback()
         self.assertQuerysetEqual(a.others.all(),['<M2mB: M2mB object>'])
 }}}

 The test explicitly rolls  back what it's done and then tries to check
 that what it did wasn't rolled back?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/16818#comment:15>
Django <https://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