You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation is unclear about native versioning's use of temporary_transaction table. Furthermore, should the temporary_transaction table be missing, even no warning is emitted.
I am using (trying to use) SA-C'nuum with Pyramid / SQLAlchemy / zope.transaction extension, with make_versioned(options=dict(native_versioning=True)); Alembic autogeneration works, triggers are created correctly, but seemingly nothing creates the temporary_transaction implicitly. Took a while even to find out why nothing is being versioned.
The docs should be clarified about this. Furthermore, which SQLAlchemy event is supposed to trigger the creation of the temp table?
The text was updated successfully, but these errors were encountered:
I looked into this again, and the transaction table does indeed have transactions, even though no changes are recorded.
I suspect this occurs because I am using alembic migrations with native versioning; the create_triggers of transaction.py is never called in that case.
The documentation is unclear about native versioning's use of
temporary_transaction
table. Furthermore, should thetemporary_transaction
table be missing, even no warning is emitted.I am using (trying to use) SA-C'nuum with Pyramid / SQLAlchemy / zope.transaction extension, with
make_versioned(options=dict(native_versioning=True))
; Alembic autogeneration works, triggers are created correctly, but seemingly nothing creates the temporary_transaction implicitly. Took a while even to find out why nothing is being versioned.The docs should be clarified about this. Furthermore, which SQLAlchemy event is supposed to trigger the creation of the temp table?
The text was updated successfully, but these errors were encountered: