Replies: 1 comment 2 replies
-
|
Hi @ope-nz, Sorry if the documentation was not clear on this point. In the current implementation, the cloud database must use the same schema as the local database. Your approach is absolutely correct. Alternatively, you can create a new cloud database with the same tables and simply enable sync on the cloud side as well, without uploading the database itself. We are currently working on a new migration feature, which should be released soon, that will remove this limitation. With the new workflow, users will be able to start from an empty database either in the cloud or on the edge, and the schema will be automatically synchronized during the first sync roundtrip. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Can I just clarify if the cloud database must have the schema or can it be empty? This wasn't explicit in the docs.
I've got my sync up and running but I had to upload a copy of my sync enabled database ie I had my local DB, enabled tables for sync and then uploaded that DB to SQLite Cloud.
Is that the correct order of operations or would the schema be created?
Beta Was this translation helpful? Give feedback.
All reactions