Re comment 13, @Rolf: Your question concerned the sql backend, not the file backend. That's a new discussion - you should move that to a new bug which deals with the SQL backend.
Re comment 12: I'd like to commit this patch. I think it is a reasonable compromise to fix the bug and yet doesn't loose too much of backward and forward compatiblity.
However, the discussion in August still had one issue open, https://lists.gnucash.org/pipermail/gnucash-devel/2008-August/023757.html , the recognition of book closing transactions. I didn't understand how Charles' patch would "screw up" if book closing transactions are present. As I understand it, we need to add a marker that indicates a transaction was automatically created. I've added such a marker in r17731, awaiting back-port.
Re comment 13, @Rolf: Your question concerned the sql backend, not the file backend. That's a new discussion - you should move that to a new bug which deals with the SQL backend.
Re comment 12: I'd like to commit this patch. I think it is a reasonable compromise to fix the bug and yet doesn't loose too much of backward and forward compatiblity.
However, the discussion in August still had one issue open, https:/ /lists. gnucash. org/pipermail/ gnucash- devel/2008- August/ 023757. html , the recognition of book closing transactions. I didn't understand how Charles' patch would "screw up" if book closing transactions are present. As I understand it, we need to add a marker that indicates a transaction was automatically created. I've added such a marker in r17731, awaiting back-port.