voussoir
d88db08693
If a @transaction method makes calls to other @transaction methods, and one of those nested calls makes a commit, and then the outer call raises an exception, then the outer call will not rollback properly because its savepoint is no longer in the savepoint stack. So let's warn the user if that happens. Should this raise an exception instead of just warn? Not sure, I mean the data is already committed. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| constants.py | ||
| decorators.py | ||
| exceptions.py | ||
| helpers.py | ||
| jsonify.py | ||
| objects.py | ||
| photodb.py | ||
| searchhelpers.py | ||
| tag_export.py | ||