Summary: | IBAN, BIC, and National Account Number "disappear" from the DB | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | jose bernardo silva <bernardo> |
Component: | database | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 4.8.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
jose bernardo silva
2018-12-16 14:46:02 UTC
To try to work around this bug, I saved a new database from inside kmymoney 4.8.2. I was informed some information would be deleted, and indeed the tables kmmPayeeIdentifier, kmmNationalAccountNumber and kmmIbanBic are removed, and kmmPayeesPayeeIdentifier is emptied. This allows starting to fill the IBAN/BIC and National Account Number for the payees, but after some time, entries disappear from kmmPayeeIdentifier, kmmNationalAccountNumber and kmmIbanBic (only the ones for the last payee edited are there), while kmmPayeesPayeeIdentifier still has entries for all payees edited. This causes the same errors of payeeIdentifier not found. Is this problem also present if you use the XML storage (.kmy file) instead of the database? That would help determine if the problem is in the database code or in the IBAN/BIC related code. I've saved the data as XML/.kmy, and I've now added IBAN, BIC and National Account Number for 4 payees. They are not lost or corrupted, even after closing and opening the file several times with different changes on each session, so I'd say the issue very probably is in the database code. Possibly it wasn't updated for the new tables? I've noticed that when I save to a database, that tables are removed and emptied, as I noted in comment #1 Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |