[kmymoney] [Bug 410994] Losing transactions after 8000+ DB to KmyFile

Ralf Habacker bugzilla_noreply at kde.org
Mon Aug 19 21:32:54 BST 2019


https://bugs.kde.org/show_bug.cgi?id=410994

--- Comment #12 from Ralf Habacker <ralf.habacker at freenet.de> ---
So you are saying that your primary file is a kmy or xml file and after
exporting to sqlite the sqlite database is broken ? 

I did the opposite and took the "sql lite db sample" sqlite database as primary
source. I added some debug code to 
void MyMoneyStorageXML::writeTransaction(QDomElement& transaction, const
MyMoneyTransaction& tx)
{
  if (tx.memo() == "T000000000000008308")
      qDebug() << tx.memo();
  tx.writeXML(*m_doc, transaction);
}

did set a breakpoint at the qDebug() output and exported the sqlite database to
an xml file.
I saw that transaction 'T000000000000008308' has 2 splits while the next
account related transaction 'T000000000000008311' did not have any splits
although the loaded sql database showed that it should have. I used the
following sql command to get the splits: 

select kmmSplits.splitId, kmmSplits.accountId, kmmSplits.postDate,
kmmTransactions.id from kmmSplits, kmmTransactions where
kmmSplits.transactionId = kmmTransactions.id

0|A000331|2019-07-08|T000000000000008308
1|A000291|2019-07-08|T000000000000008308
.. 
0|A000331|2019-07-10|T000000000000008311
1|A000284|2019-07-10|T000000000000008311

It looks to me that exporting to an kml or xml file from a sqlite database is
also broken independently from an import into a sqlite database.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the KMyMoney-devel mailing list