Good morning everyone,
I’m currently running KMY on Ubuntu 22.04 in the basic format .kmy of datas.
I’ve tested it with MariaDB and as it worked fine i would like migrate on it.
Following several tests, i encountourned difficulties with the migration: i did by export through qif files from kmy file and import them into KMyMoney MariaDB format.
What happened: lot of operations appeared 2 or 3 times due to crossed operation between different accounts (transfert operations). That generated lot of work to deduplicate everything!
Did i miss something? or did i wrong way to do this migration?
Is there any other process to migrate all my accounts (in 1 time for example by “converting KMY file”) to avoid those duplicated operations?
Thanks a lot in advance for your advises and have a beautiful day.
I’ve added the kmymoney tag to the post, so it will be more likely to be seen by more people who can help.
I’m not quite sure what you mean by migration. We usually use that to mean migrating your data to a new PC. If you just mean you want to switch from saving your data as a regular .kmy file to storing it in an SQL database, that is actually very easy. Just open your data file by starting KMyMoney, and then do Save As… and select SQL.
One thing to remember is that although the program stores your data in the SQL database, it only writes out the data (all the data) when you do File/Save. Data is not saved as you enter or edit each transaction. That means it is still not safe for two people to be using the same data at the same time.
Let us know if you have any further questions.
Hi ostroffjh
Thanks a lot for your helping answer !
what a numpty i’am to not see the save as option …
it’ runs well !
I’am aware on the ram way of working of KMyMoney and so i know it could not possible to work simultaneously by different persons in the database.
I’ve seen the message when we save as SQL database but what is there a real risk to work with SQL or is it due to the previous point about data are not saved after each transaction?
I would like to notice a possible small bug in the display on the home screen: numbers of marqued/compensated/not marqued transactions are wrong. Only columns “!M” and “!R” are populated but with the same figure: # of not marqued transaction till the current date!
Have a beautiful day
Capture d’écran du 2024-10-08 07-59-39|117x378
That image is probably correct. A transaction can be not marked, cleared, or reconciled. “!R” is not reconciled, which includes both not marked and cleared. If there are no cleared transactions then !R will be the same as !M.
However, if you do have any transactions set to Cleared, then that image is wrong.
Good morning Ostroffjh
Apologize for my late answer.
Thanks for details, and in fact, the situation is correct regarding your explanation!
However, display the # of operations not marked (no R no C) should be interesting for a complete view from my point of view!
Could i have you point of view on another thing?
When i use the mariadb instead of kmy file, kmymoney becomes slow (and sometimes very slow) when starting and each time i save datas.
It’s annoying and not user friendly.
Do you have any idea on what could generate that and, if yes, how to solve it?
(reminder: i use mariadb implementation on Asustor NAS, native implementation via application central, not through docker).
Thanks in advance and have a beautiful day.
(1) Yes, all data from the DB is loaded into memory when opening it and all is saved back when saving it. We know that this is not how a DB works, but that is what the current implementation of that backend provides.
(2) Fix the code. Current developer bandwidth does not allow to tackle it, though.
Hi Ipwizard
Thanks a lot for your clear answer.
Have a nice day
