Bug 397675 - cannot connect to kmysql database because of prepended slash
Summary: cannot connect to kmysql database because of prepended slash
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: database (show other bugs)
Version: 5.0.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
: 400502 415378 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-08-20 18:11 UTC by adoII
Modified: 2019-12-22 06:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.2


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description adoII 2018-08-20 18:11:46 UTC
I just compiled kmymoney5 and cannot open my KMyMoney mysql and cannot connect to my mysql database because of a prepended / to the database name.
Debug Output:
Error in function int MyMoneyStorageSql::open(const QUrl&, int, bool) : opening database
Driver = QMYSQL, Host = localhost, User = root, Database = /KMyMoney
Driver Error: QMYSQL: Unable to connect
Database Error No 1049: Unknown database '/KMyMoney'
Text: Unknown database '/KMyMoney' QMYSQL: Unable to connect
Error type 1
Executed: 
Query error No -1:  
Error type 0
Something magically prepends the slash to the database name, i did not enter it
Comment 1 Thomas Baumgart 2018-08-21 12:33:10 UTC
Can you try to build from master instead of 5.0.1 and report back if this solves the issue for you? I think commit c5a3c44b2a341d6efc1a55bc55dcff9ff5a594c8 should help.
Comment 2 adoII 2018-09-10 14:42:39 UTC
Sorry, took me some time to compile Master.
The problem is still the same, just a slash too much
Comment 3 Thomas Baumgart 2018-09-10 19:52:25 UTC
I cannot duplicate this problem with current 5.0 branch which is the same code base as master wrt to db code. Maybe it complained about a missing password. That was another problem I just fixed in the 5.0 branch.
Comment 4 Thomas Baumgart 2018-10-31 06:48:37 UTC
*** Bug 400502 has been marked as a duplicate of this bug. ***
Comment 5 Thomas Baumgart 2019-12-22 06:48:38 UTC
*** Bug 415378 has been marked as a duplicate of this bug. ***