Summary: | Crash Kmymoney after connection to mysql | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Josef Leo Bureš <leo> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | fvilas, onet.cristian, ppslim+kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kmymoney/dcf351abba5323e07f222677206e23cd645af118 | Version Fixed In: |
Description
Josef Leo Bureš
2012-06-03 12:24:25 UTC
This looks a lot like bug 263983, which was fixed in source on 2012-04-27. I am not familiar enough with Debian Squeeze to tell when it pulled the source from git, though. Can someone who is provide some guidance here? Oops... I need to read dates more carefully. The fix was in 2011, so the fix is almost certainly included. Something else must be going on. It looks like the database exists, or it would not have gotten this far in the code. The main reasons for a failure of -1 with no details are flaky connections (there is a recent fix for that one), an empty database because of never doing a "save as database", and access issues to the data in the database. @Josef: can you provide a little more detail, so we can rule out some or all of the above suggestions? Could you please provide the details requested by Fernando? I experienced this and a lot more on Windows. The SQL used to populate this table does not seem to be correct. Query as taken from the Generate Database SQL screen. INSERT INTO kmmFileInfo (version, created, lastModified, baseCurrency, institutions, accounts, payees, transactions, splits, securities, prices, currencies, schedules, reports, kvps, dateRangeStart, dateRangeEnd, hiInstitutionId, hiPayeeId, hiAccountId, hiTransactionId, hiScheduleId, hiSecurityId, hiReportId, encryptData, updateInProgress, budgets, hiBudgetId, logonUser, logonAt, fixLevel) VALUES (6, 2013-12-31, 2013-12-31, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 'N', NULL, NULL, NULL, NULL, 4) Exact error when run manually from MySQL Workbench: 1 row(s) affected, 2 warning(s): 1265 Data truncated for column 'created' at row 1 1265 Data truncated for column 'lastModified' at row 1 Wrapping the dates for these columns in quotes fixed this. This also allowed me to get past this error whilst trying to open the database. Git commit dcf351abba5323e07f222677206e23cd645af118 by Fernando Vilas. Committed on 31/12/2013 at 22:34. Pushed by fvilas into branch 'master'. Delimit date strings in initial DB creation SQL. Everywhere else uses bind variables, so this should fix it. M +6 -2 kmymoney/mymoney/storage/mymoneydbdef.cpp http://commits.kde.org/kmymoney/dcf351abba5323e07f222677206e23cd645af118 |