You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 13, 2024. It is now read-only.
Have you had any thoughts on how you might want to do reverse migrations? I'm likely to have some time to implement this and would want to do it in a way that lines up with your plans.
The text was updated successfully, but these errors were encountered:
There isn't a way to do this automatically without storing a copy of the database (or the modified records) before the migration. It is possible to build your own rollback mechanism, but you'd have to fork the repo. That could look something like:
Hi @kevlend,
... I know it's a off topic, but would you care to comment on why you don't use firestore anymore.. maybe you found a better alternative? I ask because I like the real time aspect of firestore, but I really miss schemas, relations and mature toolings. Thank you :-)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Have you had any thoughts on how you might want to do reverse migrations? I'm likely to have some time to implement this and would want to do it in a way that lines up with your plans.
The text was updated successfully, but these errors were encountered: