It very much depends on how periods work... You may need to change
a bunch of pointers for transactions that were listed in the "current"
period but need to get moved into the "new" period...
However I acknowledge that this doesn't happen frequently (once a
month? once a quarter?).
-derek
"Derek Neighbors" <[EMAIL PROTECTED]> writes:
> Derek Atkins said:
> > I can certainly imagine wanting to lock multiple tables if you are
> > performing the "end of period" closing..
>
> I am not sure I would use table locks to close periods. Generally a flag
> of sorts gets processed saying a period is closed, preventing any further
> transactions against said period. I wouldn't see it necessary to lock the
> tables.
>
> Derek Neighbors
>
>
--
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
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
