Closed kilbot closed 1 month ago
Hi @kilbot Yes the internally used schema of RxState was changed because the previous one was just wrong and was not valid against any stored document. As RxState is in beta, I have no clear migration strategy. Maybe the easiest way is to use a new RxState in a different namespace and move the whole state data as big JSON to that new state.
Edit: You could also use the storage migration plugin.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. Please update it or it may be closed to keep our repository organized. The best way is to add some more information or make a pull request with a test case. Also you might get help in fixing it at the RxDB Community Chat If you know you will continue working on this, just write any message to the issue (like "ping") to remove the stale tag.
The update to 15.25.0 seems to have changed the RxState schema, which throws the DB6 error. It's unclear to me how to correctly migrate RxState data to the new version.