mirror of
https://github.com/Kunzisoft/KeePassDX.git
synced 2025-12-04 15:49:33 +01:00
Add "Merge from" and "Save a copy to"
@@ -22,11 +22,15 @@ For more information on why not to integrate directly the Cloud APIs: [#342](htt
|
|||||||
|
|
||||||
There are 3 commands in KeePassDX to manage the synchronization :
|
There are 3 commands in KeePassDX to manage the synchronization :
|
||||||
- **Save data** : As the name suggests, it allows you to save the local data of the open database in the open data stream from its URI. This is the conventional method used to update the data on the reference medium.
|
- **Save data** : As the name suggests, it allows you to save the local data of the open database in the open data stream from its URI. This is the conventional method used to update the data on the reference medium.
|
||||||
- **Merge data** : Retrieves the data from the URI and merges it with the local data. _Please note that this method does not automatically save the database even if the automatic database save setting is enabled. You will have to save the database manually after a merge if that is what you want._
|
- **Merge data** : Retrieves the data from the URI and merges it with the local data. This command does not ask for a credential, if you change the main password, use **Merge from...**. _Please note that this command does not automatically save the database even if the automatic database save setting is enabled. You will have to save the database manually after a merge if that is what you want._
|
||||||
- **Reload data** : Retrieves data from the URI and deletes local data. Use this method if you want to reset the data in your database with the data in the storage medium.
|
- **Reload data** : Retrieves data from the URI and deletes local data. Use this method if you want to reset the data in your database with the data in the storage medium.
|
||||||
|
|
||||||
*If external modifications are made to the data linked to the URI, a warning message will alert you. But it is possible that this warning message is not displayed because the event has not been correctly sent, in this case, you just have to make a merge or reload the data.*
|
*If external modifications are made to the data linked to the URI, a warning message will alert you. But it is possible that this warning message is not displayed because the event has not been correctly sent, in this case, you just have to make a merge or reload the data.*
|
||||||
|
|
||||||
|
In addition to the commands described above, it is possible to use more advanced derived commands:
|
||||||
|
- **Merge from...** : Performs a merge with the same characteristics as the **Merge data** command but with a different URI file. The main credentials of the database to be merged will always be requested. It is possible to merge databases of different versions with this command. (For example: possible to merge a .kdb v1 database into a .kdbx v4 database)
|
||||||
|
- **Save a copy to...** : Saves current data to another specified file (URI). The data of the current URI are not modified.
|
||||||
|
|
||||||
## Synchronization application
|
## Synchronization application
|
||||||
|
|
||||||
In addition, there are applications that synchronize files on a continuous basis. This allows you to retrieve and send files transparently in the background when a file is updated. Very useful if your file manager does not have this feature.
|
In addition, there are applications that synchronize files on a continuous basis. This allows you to retrieve and send files transparently in the background when a file is updated. Very useful if your file manager does not have this feature.
|
||||||
|
|||||||
Reference in New Issue
Block a user