Changes between Initial Version and Version 1 of Ticket #16490, comment 3
- Timestamp:
- Jul 21, 2011, 9:38:23 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #16490, comment 3
initial v1 1 I see the first error (`modeltests.select_for_update.tests.SelectForUpdateTests.test_block`) when running tests with a pristine checkout of trunk against MySQL 5.1.58 so this doesn't seem to be introduced by your patch for #11665. Graham King tells us he doesn't see it with Maybe tehre is some change of behavior in MySQL betwen 5.1.54 and 5.1.58? What version are you using?1 I see the first error (`modeltests.select_for_update.tests.SelectForUpdateTests.test_block`) when running tests with a pristine checkout of trunk against MySQL 5.1.58 so this doesn't seem to be introduced by your patch for #11665. Graham King tells us he doesn't see it with 5.1.54. Maybe tehre is some change of behavior in MySQL betwen these two versions? What version are you using? 2 2 3 But I don't see the second one (`modeltests.select_for_update.tests.SelectForUpdateTests.test_unsupported_nowait_raises_error`), this is strange because the !SelectForUpdateTests tests [https://code.djangoproject.com/browser/django/trunk/tests/modeltests/select_for_update/tests.py#L21 inherits] from !TransactionTestCase and in theory shoudn't be affected by your changes to !TestCase handling of transactions in #11665.3 But I don't see the second one (`modeltests.select_for_update.tests.SelectForUpdateTests.test_unsupported_nowait_raises_error`), this is strange because !SelectForUpdateTests [https://code.djangoproject.com/browser/django/trunk/tests/modeltests/select_for_update/tests.py#L21 inherits] from !TransactionTestCase and in theory shoudn't be affected by your changes to !TestCase handling of transactions in #11665. 4 4 5 5 I tried with both Python 2.6 and 2.7, MySQL storage backend is InnoDB.