summaryrefslogtreecommitdiff
path: root/tests/test_postgresql.py
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2021-10-04 15:15:16 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2021-10-04 19:23:45 -0400
commited3428ec969d12befe7bbbe5c8b6b34ffea29e2e (patch)
treee3febcbce966b8ac3a0c26e567e46b50bbdcd310 /tests/test_postgresql.py
parentd95e15cac59dc449f712f51183462a8688a51086 (diff)
downloadalembic-ed3428ec969d12befe7bbbe5c8b6b34ffea29e2e.tar.gz
frame a transaction around autocommit
Fixed issue where the :meth:`.MigrationContext.autocommit_block` feature would fail to function when using a SQLAlchemy engine using 2.0 future mode. Change-Id: I851573424c7cde2595ae22c816ec6580d7cab248 Fixes: #944
Diffstat (limited to 'tests/test_postgresql.py')
-rw-r--r--tests/test_postgresql.py5
1 files changed, 5 insertions, 0 deletions
diff --git a/tests/test_postgresql.py b/tests/test_postgresql.py
index b41c383..dc0f544 100644
--- a/tests/test_postgresql.py
+++ b/tests/test_postgresql.py
@@ -48,6 +48,7 @@ from alembic.testing.env import clear_staging_env
from alembic.testing.env import staging_env
from alembic.testing.env import write_script
from alembic.testing.fixtures import capture_context_buffer
+from alembic.testing.fixtures import FutureEngineMixin
from alembic.testing.fixtures import op_fixture
from alembic.testing.fixtures import TablesTest
from alembic.testing.fixtures import TestBase
@@ -457,6 +458,10 @@ class PGAutocommitBlockTest(TestBase):
)
+class PGAutocommitBlockTestFuture(FutureEngineMixin, PGAutocommitBlockTest):
+ pass
+
+
class PGOfflineEnumTest(TestBase):
def setUp(self):
staging_env()