qof_commit_edit_part_2 commit, then delete
phil.longstaff at yahoo.ca
Thu Nov 28 08:17:50 EST 2013
In the sql backend, I think the commit may be what triggers a DELETE statement.
From: John Ralls <jralls at ceridwen.us>
To: GnuCash development list <gnucash-devel at gnucash.org>
Sent: Wednesday, November 27, 2013 7:45:03 PM
Subject: qof_commit_edit_part_2 commit, then delete
As it now stands, we run the commit code, then check priv->do_free and run the destroy callback if it’s true.
Wouldn’t it make more sense to *not* run the commit code if we’re destroying the instance?
gnucash-devel mailing list
gnucash-devel at gnucash.org
More information about the gnucash-devel