Hello, I'm looking for a way track changes to table rows, very much like described in this Stackoverflow question <https://stackoverflow.com/questions/39308396/how-to-do-versioning-with-a-history-table-in-flask-sqlalchemy-preferably-wit> .
SA supports versioning objects as described in the documentation: http://docs.sqlalchemy.org/en/latest/orm/examples.html#versioning-objects Does this approach work for inherited classes as well? I mean: can I version a class which doesn't have a table but is a subclass of a joined table inheritance <http://docs.sqlalchemy.org/en/latest/orm/inheritance.html#joined-table-inheritance>? Or will I need to version the base class which has the table associated (something I'd like to avoid because I'd version much of what would not need versioning). Then there is SA Continuum <https://github.com/kvesteri/sqlalchemy-continuum>, which seems more flexible but perhaps a little too much for my needs. With projects like Continuum I'm always a bit worried about support and maintenance—any experiences with it? Does that support table inheritance? Thanks! Jens -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
