Fix 500 on customer revision when revision_history table is missing
Deployed databases can persist without the revision_history table, causing /play/<token>/revise to crash with sqlite3.OperationalError. - log_revision() now creates the table on the fly if it is missing. - app.py runs init_db() at import time (safe CREATE TABLE IF NOT EXISTS) so new deployments auto-create missing tables on startup. Bump patch version 0.4.0 -> 0.4.1.
This commit is contained in:
parent
7ab8388741
commit
3f9de1449c
4 changed files with 37 additions and 10 deletions
2
VERSION
2
VERSION
|
|
@ -1 +1 @@
|
|||
0.4.0
|
||||
0.4.1
|
||||
|
|
|
|||
Reference in a new issue