mirror of
https://github.com/apache/superset.git
synced 2024-09-17 11:09:47 -04:00
087c47a37e
* Fixing the specific issue * Added an additional fix for a similar error in #529 Background: - When an object is modified by SQLAlchemy, it is invalidated so need to be fetched again from the DB - If there's an exception during a transaction, SQLAlchemy performs a rollback and mark the connection as dirty. Bug: - When handling exceptions, the exception handler tries to access the name of the cluster in the main object. Since the name has been invalidated due to a write, SQLAlchemy tries to fetch it on a 'dirty' connection and spits out an error. Solution: - Fetch the information for handling the exception before starting the process. |
||
---|---|---|
.. | ||
assets | ||
bin | ||
data | ||
migrations | ||
static | ||
templates | ||
translations | ||
__init__.py | ||
ascii_art.py | ||
config.py | ||
forms.py | ||
models.py | ||
utils.py | ||
version.py | ||
views.py | ||
viz.py |