id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 1746,Tests involving rollback on MySQL 4.1 should handle failures on non-transaction-supporting tables,pb@…,nobody,"I've only tested this with MySQL 4.1.x. I don't know enough to debug it effectively at the moment, but wanted to make sure it got recorded. Transaction support detection is tricky in MySQL, since the MySQL version and the table storage type are both factors. I'm also unsure what *should* happen in transaction tests with a DB that doesn't support transactions. {{{ $ ./runtests.py Running tests with database 'mysql' 'transactions' module: API test failed ====================================== Code: 'Reporter.objects.all()' Line: 38 Expected: '[Alice Smith, Ben Jones]\n' Got: '[Alice Smith, Ben Jones, Carol Doe]\n' 'transactions' module: API test failed ====================================== Code: 'Reporter.objects.all()' Line: 48 Expected: '[Ben Jones]\n' Got: '[Ben Jones, Carol Doe]\n' 'transactions' module: API test failed ====================================== Code: 'Reporter.objects.all()' Line: 59 Expected: '[Ben Jones, Carol Doe]\n' Got: '[Carol Doe, Ben Jones, Carol Doe]\n' 3 errors: }}} (""Tests"" should be added as a Component in Trac, too, I think) ",defect,closed,"Database layer (models, ORM)",,minor,fixed,,,Accepted,0,0,0,0,0,0