finite prism
Hi,
Im trying to update my databases from the CLI. I did a test with one of my dev databases and my data all became n/a.
What I did was pull the latest collection with appwrite init collection then push it back up to the same DB. There were no changes to the structure but the data seems to be gone.
The documents are there but everything is n/a
Is there a way to deploy a collection without loosing data?
finite prism
Deploying collection updates without losing data
hard stone
Hi,
Im trying to update my databases from the CLI. I did a test with one of my ...
Yes, that's expected with the CLI at the moment because the attributes and indexes get wiped and then redeployed. There should be a warning about data loss when deploying.
If you're going to make changes after going to prod, you might want to create scripts using a server SDK
finite prism
Ah yea. It said you "may" lose data which I assumed would be the case if we changed or removed database attributes. All good though. Thanks 🤙
hard stone
[SOLVED] Deploying collection updates without losing data
stable pelican
I just did this and blew up my collections. The docs (https://appwrite.io/docs/command-line-deployment#deployCollections) say "The Appwrite CLI also helps you migrate your project's databases and collections from a development server to a production server." I guess that's technically not true since it will wipe your entire production server 😅
