Bug 349425 - data problem with kmmcurrencies table.
Summary: data problem with kmmcurrencies table.
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: database (show other bugs)
Version: 4.7.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-20 21:04 UTC by John McKown
Modified: 2021-02-24 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John McKown 2015-06-20 21:04:40 UTC
Using PostgreSQL 9.4.3 on Fedora 22, x86_64, I had a problem with the "Save as database" function. There were two (or three?) different problems with the data in KMyMoney as distributed in Fedora and the SQL definition of the kmmcurrencies table. The first was that the isocode in that table is defined as "char(3)", but there are two currencies whose codes are more than three characters in length: Bitcoin (code is "bitcoin") and the "Dow Jones Industrial Average (DJIA)" whose code is "DJIA". I "patcheded" this by changing the column definition to "text". The other data problem is the "symbol1" fields in a "smallint" and the data value for the "Iranian Rial" is 65020. I "patched" this by making symbol1 an "int" instead. I also changed symbol2 and symbol3 in the same way, just to be "safe". After making these changes to the DDL, I was able to successfully use the "Save as database" function. I am also able to use this database with no problems. At least for the last 3 minutes, that it <grin>. In any case, I don't know if this is a problem with the SQL DDL or a problem with the data.
Comment 1 Jack 2021-01-25 23:44:22 UTC
It looks like this has never been addressed - the column definitions are still as described in Comment 1.  Are you no longer using the SQL back end, or are you continuing to patch your local version?  (What are your current versions of KMM and Postrgresql?)
Comment 2 Bug Janitor Service 2021-02-09 04:33:12 UTC
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!
Comment 3 Bug Janitor Service 2021-02-24 04:33:17 UTC
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!