[kmymoney] [Bug 353555] Database backend is much slower than standard kmy format

Tony Bloomfield tonyb.lx at ntlworld.com
Mon Mar 29 10:18:25 BST 2021

On 28/03/2021 14:15, jesse wrote:
> https://bugs.kde.org/show_bug.cgi?id=353555
> --- Comment #9 from jesse <jvapr27 at yahoo.com> ---
> I still have not had time to try to figure out if the database has indexes or
> not. I don't use the application with the database option. 
> >From what Martin said, the real need is based on using external programs to
> query the sqlite database. Without a way to know all the use cases, it may be
> best to either include documentation in the manual as to how and when a user
> would want to add indexes for their querying, or to add a few indexes to help
> our 80% of the use cases. 
> However, I think the decision should be made as to whether saving to the sqlite
> format was intended for this purpose or not. 
> If not, then perhaps there are no further changes required.
As the original developer of the database module, my main reason for
producing it was the ability to extend the functionality of KMM for my
own purposesĀ  Using mysql rather than sqlite, I have triggers and
routines and extra tables which enable me to do my annual tax return in
a day rather than a week. My design didn't require any indexes, and
since the initial method of operation was, as now, load the database and
save it on exit, there didn't seem to be much need for them.

Later the code was improved (not by me) to use the database in the
conventional sense, committing updates to the database as they occurred.
In that case, indexes were added to speed up the process. Unfortunately,
a later rewrite reverted to the load/save method, where offhand I can't
really see much need for indexing.



More information about the KMyMoney-devel mailing list