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

design migration strategy #78

Open
imranariffin opened this issue Mar 8, 2019 · 2 comments
Open

design migration strategy #78

imranariffin opened this issue Mar 8, 2019 · 2 comments

Comments

@imranariffin
Copy link
Member

imranariffin commented Mar 8, 2019

I realize we maybe need to force client to fetch migration script from server, otherwise there is no way the client can get the latest migration scripts without upgrade or codepush.

I have sketched some rough strategy but I'm not sure if this is over the top nor do I know what's the best practice for mobile database migration, but here it is:

migration-strategy-v1

@cglotr
Copy link
Member

cglotr commented Mar 8, 2019

@imranariffin how about we come up with the initial DB design for the MVP (message group support) for both backend & frontend. Then we can go over some DB update/migration scenario. I think doing the exercise with the DB design in hand will help us evaluate the best approach to this problem

Do you think you can finish the DB design frontend & backend by this week's meeting?

@imranariffin
Copy link
Member Author

imranariffin commented Mar 8, 2019 via email

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

No branches or pull requests

2 participants