From: Tim L. <guy...@gm...> - 2013-02-27 18:48:46
|
John Ralls-2 wrote > Transactions are what makes using a database like berkeleydb worthwhile in > an app like Gramps: They ensure atomicity, consistency, integrity, and > durability. Each operation that you want to be atomic should be wrapped in > a transaction, and the transaction should be committed at the successful > end of the operation or rolled back on failure (with appropriate logging > and sequestration of the failed data for analysis and correction, of > course). Just to be clear, I wasn't suggesting removing any transactions, just discussing how much is done in one transaction. I still don't understand how doing less in one transaction (making a separate transaction for each citation merge) can possibly be as fast. Surely data has to be really written at the end of each transaction, and writing to disc is slower than processing the accumulated transaction in memory? John Ralls-2 wrote > Aside from that, yes of course make only one "empty" citation per source. > It's dumb to do otherwise, and the results are really annoying, never mind > the performance impact. Good, I'll make that change next time I get to import processing. -- View this message in context: http://gramps.1791082.n4.nabble.com/Gramps-4-0-0-beta1-tp4658903p4659041.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |