Thank you both Jonathan and Kirk for your helpful comments. I am leaning more and more towards using a versioning/history solution. If I can figure out a way to incorporate a approved flag into the history tables produced by something like SQLAlchemy-Continuum, it should meet all the requirements and provide additional functionality for 'free'
On Sunday, July 15, 2018 at 12:20:56 PM UTC, Kirk wrote: > > On 14 July 2018 at 19:45, Marc <brouar...@gmail.com <javascript:>> wrote: > > The application has the requirement that authorised users can add >> information to the database, but this information should not be displayed >> on the public web pages until an admin has approved it. Currently there is >> no need to hold a history of changes, only the most recent versions of the >> approved records and un-approved records. >> > > Despite the lack of a need for keeping a history of changes, it still > sounds like the versioning in history meta > <http://docs.sqlalchemy.org/en/latest/_modules/examples/versioned_history/history_meta.html> > > is what you need. You could add an "approved" boolean to the table and > pull records from the version table that are "approved" for public view, > but show the latest records to admins. You could even present admins with > the actual changes between the most recently approved record and the latest > version. > -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
