I'm building an open-source LMS with a content studio for instructors — exams, quizzes, assignments, courses.
Hit a wall with preview.
Instructors don't want a fake preview.
They want to actually take the exam they just built — real timer, real submission, real grading, state persisted across requests — then either publish it or throw everything away.
Looked at three options.
PostgreSQL schema separation is conceptually the cleanest but Django migrations get painful fast.
is_draft flags end up as conditionals in every layer.
Snapshot tables can't run real workflows.
What I actually want is pytest-style DB isolation in production.
Persistable, discardable.
Does this exist? How do systems like this usually handle it?
Hit a wall with preview.
Instructors don't want a fake preview.
They want to actually take the exam they just built — real timer, real submission, real grading, state persisted across requests — then either publish it or throw everything away.
Looked at three options.
PostgreSQL schema separation is conceptually the cleanest but Django migrations get painful fast.
is_draft flags end up as conditionals in every layer.
Snapshot tables can't run real workflows.
What I actually want is pytest-style DB isolation in production.
Persistable, discardable.
Does this exist? How do systems like this usually handle it?