Behaviour of livesync between different databases #636
Unanswered
Prince-projects
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hiya,
I have a scenario which I'm unsure of expected behavior:
Three databases:
db1 - filedb1
db2 - filedb2
db3 - filedb3
My local vault:
file1
file2
I want to swap between databases as an admin that's syncing multiple users, without it pushing my local files to the database - However, I want to be able to edit the content on each, so I can't disable livesync entirely as I need to see what's there.
Currently, when I connect to a new database, it pushes my files (file1 and file2) to the db I'm connected to (which then removes filedb1 etc)
I think the problem is that when connecting to a new database it doesn't pull the data from the existing database, therefore making me overwrite it with my stuff.
Is there a way to force replication from a database on connect/boot, so I can't ever overwrite it with my local files without forcing a sync first, so my potentially wrong (or outdated) local files don't mess with the source of truth remote files?
Effectively, the remote should be the source of truth and clients should download from it at least once before being able to change/upload new files to the remote. Is there a way to achieve this?
My end goal is to have three databases for three users, and users with the correct access to databases can swap between them and fetch the database content and update their vault to match it.
Thanks :)
Beta Was this translation helpful? Give feedback.
All reactions