Correction: the issue is more that _execute_and_instances() previously was calling session.execute(), which we're wrapping in glance. Newer versions called execute directly on the connection. If we wished to wrap this as well, we'd need to be looking out for exceptions that are specific to the many backend connections supported by SQLA.
Correction: the issue is more that _execute_ and_instances( ) previously was calling session.execute(), which we're wrapping in glance. Newer versions called execute directly on the connection. If we wished to wrap this as well, we'd need to be looking out for exceptions that are specific to the many backend connections supported by SQLA.