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
I think it’s better to clean the embedded database on every run (in-memory vs. file).
It makes it clear that you will only see outputs related to what you have coded.
For SQLite, we have no choice for now due to some limitations (#10). For Postgres, we could add an option to enable persistence across runs.
Let's keep it simple for now.
__ For performance optimization, we still keep the step that prepares the migrations. It enables almost instant database re-creation.
The text was updated successfully, but these errors were encountered:
rphlmr
No branches or pull requests
I think it’s better to clean the embedded database on every run (in-memory vs. file).
It makes it clear that you will only see outputs related to what you have coded.
For SQLite, we have no choice for now due to some limitations (#10).
For Postgres, we could add an option to enable persistence across runs.
Let's keep it simple for now.
__
For performance optimization, we still keep the step that prepares the migrations. It enables almost instant database re-creation.
The text was updated successfully, but these errors were encountered: