Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Database Migrations #34

Open
jonwinton opened this issue Mar 7, 2019 · 0 comments
Open

Database Migrations #34

jonwinton opened this issue Mar 7, 2019 · 0 comments
Assignees
@james-owen
Labels
Epic question Further information is requested

Comments

@jonwinton
Copy link
Contributor

jonwinton commented Mar 7, 2019 •
edited
Loading

Questions

  • How do we execute/track migrations?
  • How can we execute migrations defined by a specific Clay instance?
  • How do we handle the cache when running these migrations?
  • What does this mean for upgrades in Amphora? (This might be loosely connected to the cache hydration of migrated data)

Side Notes:

Add any thoughts below! Tagging @yuliyv and @mrollinsiv because we're discussed this in Slack a little.
@jonwinton jonwinton added the question Further information is requested label Mar 7, 2019
@james-owen james-owen self-assigned this Apr 18, 2019
@james-owen james-owen mentioned this issue May 3, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@james-owen james-owen

Labels
Epic question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonwinton @james-owen