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
We would like to switch to SQLModel while still retaining the functionality and history tables provided by the current implementation. We have attempted to translate the Versioned class from SQLAlchemy to SQLModel, but we have not been successful.
Is there an existing concept or approach that we can use to implement this functionality in SQLModel? Alternatively, can you provide guidance on how to use the SQLAlchemy Version class with SQLModel?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
First Check
Commit to Help
Example Code
Description
We currently use plain SQLAlchemy with revision tables based on the example provided in the following link: https://docs.sqlalchemy.org/en/20/_modules/examples/versioned_rows/versioned_rows.html
We would like to switch to SQLModel while still retaining the functionality and history tables provided by the current implementation. We have attempted to translate the Versioned class from SQLAlchemy to SQLModel, but we have not been successful.
Is there an existing concept or approach that we can use to implement this functionality in SQLModel? Alternatively, can you provide guidance on how to use the SQLAlchemy Version class with SQLModel?
Operating System
Linux, macOS
Operating System Details
No response
SQLModel Version
0.0.6
Python Version
3.9
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions