Daniel Meyer
Daniel Meyer
> So I guess, this was useless. No, in the past often a migration could be done by just running the schema-migration. This is not always possible. > So actually...
Yes you are right. You need both old versions in that case to do a stable migration from 13->14->15 and you would also need a way to determine which version...
@phal0r I think I might have missunderstood your problem. When you do a migration between sotrages or major RxDB versions, you MUST use a different database name. This is intentional...
You have to either cache the RxDatabase instance or call `.destroy()` on it before recreating it. It seems you are creating it twice for the same userId `1`. This check...
Please make a PR with a test case. You can start by editing this file: https://github.com/pubkey/rxdb/blob/master/test/unit/bug-report.test.ts
Hi @croatialu Code changes look ok but this breaks the CI, please check. Also we need at least one test to check the correctness of the new behavior.
@croatialu What is the status of this? Are you still workin on it? The collection name should be a local thing. It should be able to replicate with remotes that...
Closing this. Please ping me when you want to continue then I can reopen.
I think you are using it correctly and you found a bug. Please make a PR with a test case to reproduce the problem.
Yes this feature is missing, you can do a pull request. I think the best way to implement would be to add `RxCollection.remove$` and then observe the internal store of...