David Fahlander
David Fahlander
This has been completed. See: * [y-dexie](https://www.npmjs.com/package/y-dexie) on npm * [y-dexie](https://dexie.org/docs/Y.js/y-dexie) in docs
We tested this flow with the current version and we cannot se that the bug is there. As soon as an object is added to a table (using the /my/......
Oops there was already a dup of this #1860. It has some more details...
**Hi, and thanks for your great questions!** We've recently reviewed our storage model and updated the pricing page to provide more details. Specifically, we've now separated object storage from blob...
No, we're still storing Blobs in base64 fields in postgres tables, but a bug was solved recently regarding syncing blobs. So now it's possible to use blobs but large blobs...
> Do i have to set deactivated to true? Do i have to set type to eval? Do i have to delete the user? You can set deactivated to true...
Thanks 🙏 I'll try to reproduce
The bug is fixed in the code bases for review and test. * Client: Must use dexie@next with dexie-cloud-addon@next * Server: Must use version 2.0.11 (still only in staging)
> I am curious if there's a timeline on when the v2.0.11 server will move into production. It's in staging right now, If you want to test, please provide your...
Dexie Cloud Server production is now upgraded to version 2.0.17 (current version can always be seen on https://dexie.cloud/version) and this fix is part of it. On the client side, version...