We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently fly-start.sh and schema.sql naively create tables in the DB if they don't already exist.
fly-start.sh
schema.sql
This allows for creating a new db on first launch and preserving content when redeploying.
But we don't have a way to do migration if we alter the db structure.
Current preferred approach is what's documented here https://david.rothlis.net/declarative-schema-migration-for-sqlite/ and in this HN discussion: https://news.ycombinator.com/item?id=31249823)
The text was updated successfully, but these errors were encountered:
Remove migrations TODO from README
190de9a
It's now an issue here: #5
Another option is to use Simon Willison's SQLite utils: https://sqlite-utils.datasette.io/en/stable/cli.html#transforming-tables
He's also planning a more robust migration tool: https://twitter.com/simonw/status/1752079842538123488
Sorry, something went wrong.
keybits
No branches or pull requests
Currently
fly-start.sh
andschema.sql
naively create tables in the DB if they don't already exist.This allows for creating a new db on first launch and preserving content when redeploying.
But we don't have a way to do migration if we alter the db structure.
Current preferred approach is what's documented here https://david.rothlis.net/declarative-schema-migration-for-sqlite/ and in this HN discussion: https://news.ycombinator.com/item?id=31249823)
The text was updated successfully, but these errors were encountered: