Predicting Future Minimum Balance

[Derek Atkins]

Josh Sled <jsled at asynchronous.org> writes:

> There's still a bigger issue, though, that there's no easy way to see
> the *real* effects of those Transactions without either reimplementing a
> bunch of code, or actually creating the Transactions "on the books",
> which you generally don't want to do in a reporting context.  In other
> words, there's no way to have an "excursion" where you create a bunch of
> Transactions then roll them back.  Though I guess we could make such a
> beast using the transaction (software, not financial) mechanism of the
> engine... but keeping large transactions open doesn't strike me as a
> good idea.

It might be interesting to have an API that gives us "virtual"
transactions so we can report on them even if they don't appear in the
registers.

> In any case, probably a topic to follow up on -devel, at some point.
> But, no, there's no way to do what you'd like a present.

yeah..

> ...jsled
> http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo ${a}@${b}`

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available