tag:infinitekind.tenderapp.com,2009-01-14:/discussions/moneydance-development/2824-checking-moneydance-in-to-version-controlInfinite Kind: Discussion 2020-06-11T10:23:42Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/483966382020-06-11T10:23:37Z2020-06-11T10:23:37ZChecking Moneydance in to Version Control<div><p>It's great to hear your positive experience with using version control with the moneydance file. I'd note that the files are only binary because they are encrypted and that behind the encryption they are line-based text files. As you noted, a new file is created for each change (or set of changes if they are grouped). The tiksync/safe/trunk file represents the current state of the data on the current computer. That current state is composed from the combination of all of the incremental change files, and the processed.dct file contains a record of which incremental txn files have been incorporated into the trunk.</p>
<p>So in theory if you did have a conflict between changes on two computers you could revert the trunk and processed.dct files which would cause both clients to re-apply the incremental changes from the individual txn files.</p>
<p>Of course I always need to add the disclaimer that having syncing enabled would roll back any of these manual changes :)</p>
<p>Thanks,<br>
Sean</p>
<p>--<br>
Sean Reilly<br>
Developer, The Infinite Kind<br>
<a href="https://infinitekind.com">https://infinitekind.com</a></p></div>Sean Reilly