Hi Simon, On Sun, 07 Aug 2016 09:36:13 -0700, Simon Michael <[email protected]> wrote: > > Using a checksum for deduplication won't handle identical CSV records well, > right ? Those are unlikely with our usual banks but I think quite possible if > you consider CSV data generally.
No, that could be an issue. But with a date + unique amount it seems unlikely. The MD5 method is only the basic method. If your CSV file provides a unique ID row - which paypal does - that is used instead. > Here's my recent plan for hledger. Let reading CSV files work as it currently > does, but add a separate import command which does some additional things: > append the converted entries to the main journal file, and save a position > marker in CSVFILE.lastimport. Also when reading, if the marker file is found, > skip any CSV records before the marked position. > > This much is generic and could be used with any data format, but I think it > makes sense mainly for "import" data which you want to move into a main > journal, > and which is somewhat sequential, eg CSV, OFX QIF. It's would be harder and is > probably not needed for eg journal or timeclock files. > > For CSV specifically, I'm thinking the position marker will be the last CSV > record processed. It could be elaborated later to consider timestamps, > checksums > etc. if needed. 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. Would it work with multiple input sources? 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). best, Erik 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. -- Sent from my free software system <http://fsf.org/>. -- 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/57a76d31.5c0a620a.b5d49.4b37%40mx.google.com. For more options, visit https://groups.google.com/d/optout.
