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.

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

Add author information to all blogs and add migration blog #12

Merged
merged 4 commits into from
May 14, 2024

Conversation

zprobst
Copy link
Member

@zprobst zprobst commented May 14, 2024

No description provided.

- Nodestream keeps track of which migrations have been applied so that it can skip them in the future.

Crucially, nodestream does not track all possible schema changes.
Topological changes are not tracked, so you will need to handle those manually.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its not clear to me what "topological changes" means here. It might be good to give an example of what would need to be managed outside of the process.

@zprobst zprobst merged commit 0d953d8 into main May 14, 2024
@zprobst zprobst deleted the blog/migrations-design branch May 14, 2024 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants