On 8/7/16 10:17 AM, Erik Hetzner wrote:
That does seem a lot simpler than the method ledger-autosync uses. On the other hand it ties the system to ensuring that file ordering does not change.
Yes, it's for that case. For more randomly changing data, checksums would be more important.
Would it work with multiple input sources?
It should, each input file/source has its own position marker.
Another tricky issue might be overlap. A nice feature of ledger-autosync is that it can handle overlapping imports, e.g. importing from a file where some portion of the transactions are new and some portion are old (known).
That's the point of this scheme - to reliably import just the new CSV records from an intermittently updated bank download.
I like the idea of the position marker (contents of FILE.lastimport) being flexible, so the deduplication strategy can be changed without changing the UI.
Writing extra files is a bit of clutter, but hledger users are used to seeing FILE.csv.rules, and I think it's better to keep them visible (not dot files) to remind that they exist, can be edited/deleted to adjust the last import position, and might contain sensitive data.
PS: I’ve also updated the ledger-autosync README to include some basic information about tracking 401k and investment accounts. ledger-autosync now includes code to properly (mostly) import these type of transactions.
Nice, docs++. -- 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/no83bo%24s77%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
