| Summary: | Crash when creating a report | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | wolfgang.bachleitner |
| Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | edgaralwers, justin, nicolasb.info, onet.cristian |
| Priority: | NOR | ||
| Version: | 4.6.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kmymoney/03012f548a6501138e31b86853eb2dc6a4cccefe | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: | This is my anonimized datafile. I exported it from my mysql instance | ||
|
Description
wolfgang.bachleitner
2013-01-05 13:02:47 UTC
What type of report were you trying to create? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It does not matter which report. It also happens if I try to open a predefined report. E.G. "Einnahmen und Ausgaben, aktuelles Jahr". I cannot open any report yours Wolfgang Bachleitner -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ8tNiAAoJEKdCGcuse478SjEIAJwbKM39gSvTGAnadaJ1BPmm S2TUj9Jk541p/LYIpR9BHoYodVcne9Yp9tc67A27LUYczuZDVsClCYl8hGpW7a+L 8WMkWGfQoepp7gbWw5PXBV0M6rsct8V+sLzHUg1Uk/gJ5UQURnQ27X1Ab26nhGZB ZAR9tnH30XfNQGLWPpKEPOsdFcKfARAPkyY395/+daBkbrsVuaYWem5FilFZt3Nu PB73OazmRwWIINBHP0t/viEleBb8XzBIf/BwYlpTWT4a4XcGgxCV3QVP9dtUJBga jbwvGyfCDA9f/Q/p1aPwi7e1h/rZTW2i7qnoDNKZgf/WssKjRZ/0/LqpLqpg+aE= =5emf -----END PGP SIGNATURE----- Could it be a duplicate of bug 282107 which has already been fixed in master? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I updated from a 4.5 version, where I did not have this problem. Since I am using the version 4.6.3 this crash happens! Thank you for your answer yours Wolfgang Bachleitner -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ8u2+AAoJEKdCGcuse478nbEH/0LesNLYa/K86dtYgYhEIOln TwE7owgxgplGcSw+a4q8XcU+nHdOLOp4SuLPJ3cO4rVeyqJhOrrEalw/YsbpU54D VFOAMsEdqZci9r+osLDN9zoBxmfr4ZVT8jpEJ5RTlxB0oQviiAUUEtfbka8uzT5F JO3c3GQZK4GEttjbGKMWBfAX12Lv9bnMwNddw0XPqSZPA+gg4HRZtMWTL5BIb5Ea PIbB9umVMmbFMgkXH39c0sqg8zc9RyymMqrzh5lMs0BOvKUqJ/s1BcF6KuTrreXu tUp40TaII/yyTclLaDJd2AkUDGimsTDRtIHaWvytMwd5+1OOPbh3i1TwqxMTfFU= =EBh9 -----END PGP SIGNATURE----- *** Bug 313331 has been marked as a duplicate of this bug. *** Could we get an anonymous file to reproduce this? If you can provide the information requested in comment #6, please add it. Created attachment 76935 [details]
This is my anonimized datafile. I exported it from my mysql instance
Comment on attachment 76935 [details]
This is my anonimized datafile. I exported it from my mysql instance
In order to reproduce te bug with this attachment
1) open kmm with my datafile
2) Export to mysql
3) Open kmm connecting t mysql database containing my datafile
4) open "Valor neto desde 2/9/2011, base mensual" report
5) on the report screen, click on new
6) go to date tab, and change the interval to 'last 12 months'
7) Save the new report
I can confirm this. Before crashing there was this DB error message: Nu se poate adăuga raportul, motivul: "Error in function void MyMoneyStorageSql::writeReport(const MyMoneyReport&, QSqlQuery&) : writing Reports Driver = QSQLITE, Host = localhost, User = cristi, Database = /home/cristi/dezvoltare/testfiles/mysql Driver Error: Database Error No -1: Text: Error type 0 Executed: INSERT INTO kmmReportConfig (name, XML, id) VALUES (?, ?, ?); Query error No 19: column id is not unique Imposibil de preluat rîndul Error type 1" Git commit cad7ecbccda1d2b96122bd1fb8bb4a37d6c4f8e9 by Cristian Oneț. Committed on 30/08/2013 at 10:25. Pushed by conet into branch 'master'. Fix a crash in reports using the mysql storage backend. This crash was caused by the fact that the report, after requesting the transaction list, did not check that the transactions are inside the requested date interval. Since the date is used to compute an index in a columns list a date outside the requested interval would cause an invalid index to be computed and causing the crash. Now the report performs a validity check of the date after filtering the transactions. Also fixed the SQL backend implementation to properly filter by dates even if an empty split filter is provided. Also added a testcase for this scenario. M +15 -0 kmymoney/mymoney/storage/mymoneydatabasemgrtest.cpp M +2 -2 kmymoney/mymoney/storage/mymoneystoragesql.cpp M +7 -3 kmymoney/reports/pivottable.cpp http://commits.kde.org/kmymoney/cad7ecbccda1d2b96122bd1fb8bb4a37d6c4f8e9 Git commit 03012f548a6501138e31b86853eb2dc6a4cccefe by Cristian Oneț. Committed on 30/08/2013 at 10:25. Pushed by conet into branch '4.6'. Fix a crash in reports using the mysql storage backend. This crash was caused by the fact that the report, after requesting the transaction list, did not check that the transactions are inside the requested date interval. Since the date is used to compute an index in a columns list a date outside the requested interval would cause an invalid index to be computed and causing the crash. Now the report performs a validity check of the date after filtering the transactions. Also fixed the SQL backend implementation to properly filter by dates even if an empty split filter is provided. Also added a testcase for this scenario. (cherry picked from commit cad7ecbccda1d2b96122bd1fb8bb4a37d6c4f8e9) M +15 -0 kmymoney/mymoney/storage/mymoneydatabasemgrtest.cpp M +2 -2 kmymoney/mymoney/storage/mymoneystoragesql.cpp M +7 -3 kmymoney/reports/pivottable.cpp http://commits.kde.org/kmymoney/03012f548a6501138e31b86853eb2dc6a4cccefe *** Bug 318472 has been marked as a duplicate of this bug. *** *** Bug 322463 has been marked as a duplicate of this bug. *** *** Bug 327265 has been marked as a duplicate of this bug. *** |