Cricket Onebit wrote > Can you explain more about not being able to undo things with the SQL > backend vs XML (or point to more details)? I'm undecided about which > backend. Fully-functional and easy to install and maintain is more > important to me than a few seconds while using, unless those seconds add > up > quickly. I want to do my accounting, not trouble-shoot the installation.
With the XML backend, any modifications are kept in memory until you explicitly save the changes. (You can also setup GnuCash to auto-save at set intervals.) So if you make a major/destructive goof while editing transactions, you can always just not save and get back to your last saved state. With a SQL backend, modifications are committed immediately to the database, so there is no way to go back. That said, converting from one format to another is trivially easy and doable at any time, so it's not necessarily a big decision you have to make a priori. -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
