- identify another spot where _handle_dbapi_error() needs to do something

differently for the case where it is called in an already-invalidated state;
don't call upon self.connection

1 files changed, 28 insertions, 0 deletions

diff --git a/test/engine/test_parseconnect.py b/test/engine/test_parseconnect.py
index 4a3da7d1c..8d659420d 100644
--- a/test/engine/test_parseconnect.py
+++ b/test/engine/test_parseconnect.py
@@ -397,6 +397,34 @@ class CreateEngineTest(fixtures.TestBase):
             assert not de.connection_invalidated
 
     @testing.requires.sqlite
+    def test_cant_connect_stay_invalidated(self):
+        e = create_engine('sqlite://')
+        sqlite3 = e.dialect.dbapi
+
+        class MySpecialException(Exception):
+            pass
+
+        eng = create_engine('sqlite://')
+
+        @event.listens_for(eng, "handle_error")
+        def handle_error(ctx):
+            assert ctx.is_disconnect
+
+        conn = eng.connect()
+
+        conn.invalidate()
+
+        eng.pool._creator = Mock(
+            side_effect=sqlite3.ProgrammingError(
+                "Cannot operate on a closed database."))
+
+        try:
+            conn.connection
+            assert False
+        except tsa.exc.DBAPIError:
+            assert conn.invalidated
+
+    @testing.requires.sqlite
     def test_dont_touch_non_dbapi_exception_on_connect(self):
         e = create_engine('sqlite://')
         sqlite3 = e.dialect.dbapi