On 01-06-2016 22:34:05, Martin Blais wrote: > > One problem I haven't figured out yet: Does the hash of a transaction > > change if > > the transaction > > * gets moved to another file/location in a file > > No. > > > * gets changes (naming of the involved accounts, date, tags, other > > data) > > Yes. > > ? This would be kind of critical, as this would result in dangling > > "pointers" > > (hashes) in my database. > > I'm rather sure that the listed changes result in a change of the hash, > > don't > > they? I'm not sure how to wrap around these issues. > > > > Based on your application, I think what you should do is decide which > subset of the fields matter and derive your own unique hash from the > Transaction object. > > FYI the original hashing code is located here: > https://bitbucket.org/blais/beancount/src/7250b43b115603f5cbcc2088b2d124034ceaf766/src/python/beancount/core/compare.py?at=default&fileviewer=file-view-default#compare.py-63
This sounds like a solution for me, thanks! -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg. -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20160602161318.GM26461%40yuu. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
