refresh second pass

[Conrad Canterford]

Derek Atkins wrote:
> For example, if your 'account C' component viewing some range of dates
> registers for any changes to account C, then yes, it will get an event
> when your new transaction is entered into the database.  However, in
> that particular case, I would hope that your open 'account C'
> component would look at the new transaction, notice that the data is
> out of range, and then ignore it, doing nothing else.

Changes to previous transaction in an account *may* affect a view
outside of the period of the change. The details of the change will need
to be checked.
In particular, I am thinking of balances - both for share counts and
money counts. Any change of these values (direct or indirect) in a
non-current view but prior to the current view have to be detected. This
may be important for things like a later period reconcilation in
progress at the time of a later update (we cannot assume that people
will be sensible and not reconcile a later period while an earlier
period remain unreconciled... :-)).

Of course, none of this invalidates Dave's proposed scheme (of Derek's
or other comments). It just emphasises that we have to be careful when
using it that we really are doing things properly. It is not a foolproof
arrangement, but then, I don't think such a thing really exists.

Conrad.
-- 
Conrad Canterford (conrad@mail.watersprite.com.au)
Water Sprite Pty Ltd   | info@mail.watersprite.com.au
 GPO Box 355,          | Incorporating:
 Canberra, ACT, 2601   |   Australian Tour and Event Management (ATEM)
 Australia.            |   Ticketing Services Division
Phone: 0419 122 553    |   Catering Services Division