Server should immediately stop if migrations haven't run
mcpherrinm opened this issue · 1 comments
mcpherrinm commented
If the database is present but doesn't have any tables (because you forgot to run migrations), the server starts but returns an error for every request.
We should check at startup that all expected tables exist, and throw if they don't.
Ideally we should check that migrations have run, too, so that the DB is compatible with the code currently running.
mcpherrinm commented
fixed in d055426