Changes between Initial Version and Version 1 of Ticket #28263, comment 7


Ignore:
Timestamp:
Nov 15, 2019, 11:45:57 AM (5 years ago)
Author:
Héctor Pablos

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #28263, comment 7

    initial v1  
    11Bringing this up again because I'm facing the same issue Lokesh Dokara was facing in django 2.2.7. In my case I'm developing a database backend for [https://www.exasol.com/en/ / ExaSol].
    22
    3 I also met the problem while executing some tests, and I managed to overcome it by extending {{{django.test.testcases.TestCase}} and overwriting the {{{_enter_atomics}}} and {{{_rollback_atomics}}} methods so no transactions are started or rolled back for databases with {{{uses_savepoints = False}}} and {{{supports_transactions = True}}}, but that means I have to be careful not to modify the data, as it won't be rolled back. Using {{{TransactionTestCase}}}, which would not create any transactions, is not an option for me, as I can't truncate other databases the tests depend on.
     3I also met the problem while executing some tests, and I managed to overcome it by extending {{{django.test.testcases.TestCase}}} and overwriting the {{{_enter_atomics}}} and {{{_rollback_atomics}}} methods so no transactions are started or rolled back for databases with {{{uses_savepoints = False}}} and {{{supports_transactions = True}}}, but that means I have to be careful not to modify the data, as it won't be rolled back. Using {{{TransactionTestCase}}}, which would not create any transactions, is not an option for me, as I can't truncate other databases the tests depend on.
    44
    55The underlying issue is not only in the tests, every database backend with {{{uses_savepoints = False}}} and {{{supports_transactions = True}}} will raise exceptions in the following scenario:
Back to Top