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

Test automatic migrations #4

Open
tantaman opened this issue May 17, 2023 · 1 comment
Open

Test automatic migrations #4

tantaman opened this issue May 17, 2023 · 1 comment

Comments

@tantaman
Copy link
Contributor

  • If client upgrades and server is not upgraded, all sync connections should be terminated and no new ones established
  • server should migrate on restart if new schema file and version is available
  • client should migrate on restart / refresh under same conditions
@tantaman
Copy link
Contributor Author

Auto-migrations work well other than the fact that we do not tell the user why a migration failed.

This is a really confusing experience as a user might add a required column to a table which already has data. This will fail but it isn't entirely obvious that it would fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tantaman