-
Notifications
You must be signed in to change notification settings - Fork 237
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 in more migration types #14
Comments
What would be the best way to support custom migrations? The problem that I have is that in order to determine the source model for the migration, I have to get the metadata of the current store via My suggestion is to save the store's metadata outside of SQLCipher (by writing the serialized metadata to disc for instance). Do you see any security concerns in doing so? |
+1 for progressive migration support. |
Hello @sascha, |
@jasper-ch-chan: Sorry, I did not. I was able to get around using custom migrations so far and probably won't work on this again until summer. I'm happy to share my results then, but I think writing the metadata to disc is the only way that's with |
@sascha Thanks for your response. Please keep me posted should you make any more progress in this matter. I think I'll take a stab at this implementation and see what comes of it. I'll keep you notified if you're interested. |
Currently only a limited subset of migrations are available
The text was updated successfully, but these errors were encountered: