Re: Transaction logging and the dbi backend

Christian Stimming writes: > Am Saturday 12 June 2010 schrieb Geert Janssens: >> But I'm unhappy with that choice, because it's inconsistent. I see two >> potential uses for the transaction log: >> * Data recovery in case of a crash >> * Audit trail >> ... >> >> So there's question number one: s

Re: Transaction logging and the dbi backend

On Saturday 12 June 2010, Christian Stimming wrote: > Am Saturday 12 June 2010 schrieb Geert Janssens: > > But I'm unhappy with that choice, because it's inconsistent. I see two > > potential uses for the transaction log: > > * Data recovery in case of a crash > > * Audit trail > > ... > > > > So t

Re: Transaction logging and the dbi backend

Am Saturday 12 June 2010 schrieb Geert Janssens: > But I'm unhappy with that choice, because it's inconsistent. I see two > potential uses for the transaction log: > * Data recovery in case of a crash > * Audit trail > ... > > So there's question number one: should transaction logging be enabled f

Transaction logging and the dbi backend

Executive summary: * The engine supports transaction logging * For which backends should be enable this ? * If also enabled for mysql/postgres: where to store the logs ? Longer story with motivations: My hacking attention is currently focussed on the gnucash transaction log feature. I don't have