There is a reason databases set the bundle bit This is why, in the previous comment, I emphasized that packages do not exist at the Unix level! At the Unix level a sync utility or sync server cannot know that a DEVONThink database should be treated as a file rather than a folder and so any form of Unix syncing (whether it be Dropbox sync or ChronoSync sync with dissect packages) might easily lead to problems. You may not be aware of that problem if you forgot that you added D, but it still exists.įurthermore, next time you sync the other way round the source will have the same problem! Now there is a problem: the target contains a document (D) that is not registered in its administrative file (A’), so it will not be found in searches, it is not available to DEVONThink’s artificial intelligence, you will not find it in the group hierarchy and so on. Now the source remains and the target becomes. You let ChronoSync solve all problems by syncing from source to target (once only). You will find that A’ conflicts with A", that B’ will be transferred from source to target and D from target to source. This too is accompanied by a change in A. Suppose you have a database (package) with two documents B and C and one administrative file A (the administrative file maintains the location of B and C, the index, metadata and so on). Unfortunately if ‘dissect packages’ is selected making sure that you never do bidirectional criss-crossing is not enough to assure that everything goes well. You should only ever see operations going one way, never bidirectional criss-crossing. The “always use newest” would have amalgamated the newest version of the database, indexes and resources from different sources, yes, but they would not have complemented each other.Ĭall me paranoid but with databases I’d rather be safe and it just takes one extra click after making sure that files and databases are synced in the same direction. Not everyone is perfect, though, and running the trial sync and manually looking for bidirectional rather than unidirectional sync operations provides an extra layer of security. If you are very consistent and always make sure that everything is synced to the newest version before opening a database then letting CS always choose the newest version of the file will always be the right thing. An otherwise intact database pointing to an item that does not reside exactly at that location or which does not contain the information indexed elsewhere is still broken. Each of these need to be the version that corresponds exactly to the other items. There is a reason databases set the bundle bit and hide an extensive folder structure containing the database itself, index files, and the resources (=files) managed in the database etc inside a monolithic bundle. Thou I thought the “always use newer update” option (in CS) might make that x-cross process safer. Quote: “You should only ever see (ChronoSync) operations going one way, never bidirectional criss-crossing.”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |