#11101: Oracle fails admin_view tests when the whole suite is run -- transaction
problem?
---------------------------------------------------+------------------------
          Reporter:  mboersma                      |         Owner:  mboersma   
            
            Status:  new                           |     Milestone:             
            
         Component:  Database layer (models, ORM)  |       Version:  SVN        
            
        Resolution:                                |      Keywords:  oracle 
transaction test
             Stage:  Accepted                      |     Has_patch:  1          
            
        Needs_docs:  0                             |   Needs_tests:  0          
            
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Comment (by ikelly):

 After going through the test suite, here's what I've found:

 The views, admin_views, and model_formsets test suites are still getting a
 single 'unique constraint violated' error each.  I don't know why yet, and
 it may be unrelated, but at least that's a heck of a lot better than
 before.

 The backends test suite is getting a couple of errors that look like this:
 {{{
 DatabaseError: ORA-02091: transaction rolled back
 ORA-02291: integrity constraint (DJANGO_TEST_DEFAULT.SYS_C001650670)
 violated - parent key not found
 }}}

 And the fixtures_regress test suite is getting a failure that is caused by
 the patch:
 {{{
 ======================================================================
 FAIL: test_duplicate_pk
 (regressiontests.fixtures_regress.tests.TestFixtures)
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File
 
"/home/ikelly/projects/django.trunk/tests/regressiontests/fixtures_regress/tests.py",
 line 60, in test_duplicate_pk
     self.assertEqual(animal.id, 2)
 AssertionError: 12L != 2
 }}}
 This happens because the sequence value no longer gets decreased when the
 sequence is reset.  That's not really what the test is meant to be
 testing, however, and I would suggest that it perhaps should be replaced
 with assertGreaterEqual.

 There are a handful of other failures that don't appear to be related to
 this issue.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/11101#comment:11>
Django <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