>>>>> Martin Blais <[email protected]> writes: > Why don't you fix that problem instead of putting these annoying > constraints?
Virtual transactions in C++Ledger involve a runtime calculation that gets applied to every posting during the parsing stage. This can really add up. I had a solution before, in that I would persist the results of those calculations into a binary file. However, this increased code complexity significantly, but did not benefit most users. If you have tons of transactions, and a lot of virtual transactions, then I agree with Craig that the way to recover full speed is to use a "book opening" entry, and to simply close out the older data. You can always do this in such a way that you can still query the older data; but unless you actually need to, there are benefits to not doing so. John -- --- 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.
