> 1.1 "Duplicate Entry" drawing 10 cash twice in one day is not an error >> > > Hmm, so here's the thing, in the implementation, each transaction has a > unique signature, a "hash", which allows me to make comparisons between > sets of transactions. The transactions will only be detected as duplicates > if and only if _all_ of their fields are exactly the same. This rarely if > ever happens in practice. You probably were cut-n-pasting the same > transaction to test things out. > > The reason this exists is that it has happened a few times in the past > that in the course of importing a transaction was copied twice - clearly an > error. This check exists to detect this. > > Okay, so here's what I'm going to do: > - Make the unused account check optional; it will be available through an > optional plugin. > - Make the duplicates check optional; similarly will be available through > an optional plugin. > Those who want super tight checks will have to add the options. > Something like this: > > option "plugin" "beancount.plugins.nounused" > option "plugin" "beancount.plugins.noduplicates" > > By default unused accounts and duplicates would be allowed. > How's that? >
Implemented. https://bitbucket.org/blais/beancount/commits/01ab95c5ab260fb3d6dc34861e5111c4da3ff35d?at=default https://bitbucket.org/blais/beancount/commits/0362940c62197b2ab4b0838b5f7c754afb2ef7eb?at=default Beancount users: if you still wants these validation checks, add this to your file: option "plugin" "beancount.plugins.nounused" option "plugin" "beancount.plugins.noduplicates" -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
