When playing with it I noticed zero performance hit on High Sierra. But I also have no performance lag with XML. Mileage may vary.
Regards, Adrien > On May 17, 2018, at 9:07 AM, John Ralls <jra...@ceridwen.us> wrote: > > Should be since the SQL (including SQLite3) backend saves each change > immediately so there is no bulk saving. The initial “save as” operation might > be, but that’s a one-time hit. > > Regards, > John Ralls > > >> On May 17, 2018, at 6:35 AM, Sébastien de Menten <sdemen...@gmail.com> wrote: >> >> Is the SQLite storage format immune to the issue regarding "very long time >> to save the XML format" some users are experiencing? >> >> On Thu, May 17, 2018, 10:46 David T. via gnucash-user < >> gnucash-user@gnucash.org> wrote: >> >>> And, as I noted in January, the sql format does not get compressed, so the >>> files are much larger. >>> >>> >>> >>> On Thu, May 17, 2018 at 10:37, Adrien Monteleone< >>> adrien.montele...@lusfiber.net> wrote: Keith, >>> >>> The SQL backends are having a few issues at the moment. It would be a good >>> idea to search the list here and also to look over the bug reports on >>> Bugzilla. >>> >>> I originally used MySQL when I was running an Ubuntu box as my daily >>> machine, but changed to XML when I moved to MacOS, and then switched to >>> sqlite3 about two years ago, but had to change back to XML since the 3.x >>> series release due to several bugs related to the business features. (if >>> you don’t use those, you might not have any problems) >>> >>> If all you want is the ability to run outside queries for custom reporting >>> or data integration, then sqlite3 is probably your safest bet. MySQL and >>> Postgres are much more involved to setup and maintain. Essentially, if >>> you’re not a database admin, you probably don’t need those two or will not >>> find any advantage to the maintenance learning curve and overhead, stick >>> with sqlite3 or XML. >>> >>> As for searching the list archives, use the following syntax before your >>> search query terms: >>> >>> site:lists.gnucash.org >>> >>> However, I see that DuckDuckGo does not return any results with this >>> method. >>> >>> Google does, as well as StartPage. (the latter I find to be more privacy >>> conscious than DDG and usually provides me more relevant results.) I >>> haven’t tested any other search engines with that syntax. >>> >>> Regards, >>> Adrien >>> >>> >>>> On May 16, 2018, at 10:32 PM, Keith Keller < >>> kkel...@wombat.san-francisco.ca.us> wrote: >>>> >>>> On Thu, May 17, 2018 at 03:21:13AM +0000, David T. wrote: >>>>> I'm not sure how you looked, but this topic had been discussed for >>> many years on the list. A recent one was >>> https://lists.gnucash.org/pipermail/gnucash-user/2018-January/074315.html. >>> Another was >>> https://lists.gnucash.org/pipermail/gnucash-user/2013-September/050410.html >>> . >>>> >>>> Thanks David! That January 2018 thread was helpful. I'm not sure why >>>> DDG didn't turn it up. :( >>>> >>>> My impression is that the format really doesn't make an appreciable >>>> difference to performance, and that a SQL format might be more flexible >>>> for reporting but otherwise the formats are basically interchangeable. >>>> Does that sound like a reasonable summary? >>>> >>>> I may simply stick with XML for now since it's easy and lazy. >>>> >>>> --keith >>>> >>>> >>>> -- >>>> kkel...@wombat.san-francisco.ca.us >>>> >>>> _______________________________________________ >>>> 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. >>>> >>> >>> >>> _______________________________________________ >>> 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. >>> _______________________________________________ >>> 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. >> _______________________________________________ >> 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. > > _______________________________________________ > 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. _______________________________________________ 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.
