Update db/initialize.sql to drop/create a cache_development db
#2163
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The MO process for updating a development db snapshot will usually drop this third db, which is necessary for local caching. Solid Queue uses tables in the main db, so that's just a migration.
nimmolo
changed the title
cache_development dbdb/initialize.sql to drop/create a cache_development db
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The MO process for updating a development db snapshot will usually drop all databases, including this third
cache_developmentdb, which is necessary for local caching.The
db/initialize.sqlscript is intended to prepare mysql to import a new db snapshot, but I think without the changes in this PR, people will have to create thecache_developmentdb manually (and grant usermoprivileges) every time they update their dev db, in order to use or test Solid Cache.(Solid Queue uses tables in the main db, so that's handled by a migration.)