https://bugs.kde.org/show_bug.cgi?id=410994
--- Comment #19 from robsonsilva <evertondan...@yahoo.com.br> --- (In reply to Jack from comment #16) > This seems like it is going around in circles. I think it is appropriate to > go back to the real core problem. If you were using a sqlite database, and > found you had transactions which were seen in the ledger, but not in > reports, that is what needs to be diagnosed. Exporting to other formats may > fail to produce a complete, consistent file, but that is because there is > already a problem with the data, not because of a problem with the process > of exporting to a file, other than that it fails to notice the bad data and > notify of the problem. > > Using the sqlite database when you first noticed the problem, if you save > again as a database, and reopen the newly saved sqlite file, does anything > change, or does it show EXACTLY the same problem? Yes you are right, I got a backup with the first occurrence, there I found 2 transactions without splits. When I spoted the problem in KMY I was generating reports, so from there I generated KMY/XML data type files, these types can skip missing transactions/splits. As a consequence I could see ledger and reports working. However, when I tried to go back to sql the mess were there and became worse. I added 2 attachments: - UsingJustDB: Where I reproduced the problem described above. - GettingRidOfInvalidFirst: Where first I deleted transactions without splits and verify KMY working fine for same scenario. :) * consistency check for number of splits was a great idea ! * tks guys. -- You are receiving this mail because: You are watching all bug changes.
