Phil Longstaff <[EMAIL PROTECTED]> writes:
> I put in some special case code for now so that if a clean transaction
> is committed, each split is then committed so that dirty splits in a
> clean transaction will be written to the db. However, if a split is
> deleted from a transaction, the deletion is never committed so the db
> now has an out-of-balance tx.
>
> Two solutions:
> 1) better split handling in the register so that dirty splits are
> handled properly even if the tx has not been modified
> 2) If a split is dirty, mark the tx dirty too
>
> Comments?
I dont think the register has anything to do with this.. The engine,
however....
Maybe Chris can respond, as he's the one who's worked most recently on
the QOF commit_edit code for Transactions and Splits. It should be
the case that the Commit Transaction callback gets called when the
Splits have the do_free flag set.
-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
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel