[kmymoney] [Bug 415378] New: Leading "/" inserted before database name after creation
Landis
bugzilla_noreply at kde.org
Fri Dec 20 02:52:50 GMT 2019
https://bugs.kde.org/show_bug.cgi?id=415378
Bug ID: 415378
Summary: Leading "/" inserted before database name after
creation
Product: kmymoney
Version: unspecified
Platform: MS Windows
OS: Cygwin
Status: REPORTED
Severity: normal
Priority: NOR
Component: database
Assignee: kmymoney-devel at kde.org
Reporter: bdlightman at hotmail.com
Target Milestone: ---
Created attachment 124607
--> https://bugs.kde.org/attachment.cgi?id=124607&action=edit
Packet capture screenshot of database with leading "/"
SUMMARY
When adding a new database via Cygwin, we are able to create the database
successfully (base MySQL "mysql" DB or PostGRES DB works fine, allows KMM DB
creation), but the subsequent attempt to connect and populate the database
fails, as a "/" character is prefixed to the database name, and the database
daemon returns an error that the database does not exist.
Fairly novice at reporting on things like this, so this could be an upstream in
the Qt SQL drivers - if it appears so, would appreciate direction on how to
file there.
STEPS TO REPRODUCE
1. Set up a database host (PostGRES or MariaDB(/MySQL?)) on another host
2. Create a user with appropriate permissions to create the database.
3. File -> Save as database; enter appropriate information
3. Database is created. Packet capture shows KMM attempting to connect to the
database after creation, but using a leading "/" on the database name.
OBSERVED RESULT
Empty database is created successfully, but the subsequent attempt to connect
to and populate the database fails because of the leading "/" on the database
name.
EXPECTED RESULT
Client can connect to the database after creation, populate, read, and write.
SOFTWARE/OS VERSIONS
Windows: 10
Cygwin/X 1.20.5
XWin xdg 20170321-1
KMM 5.0.0
ADDITIONAL INFORMATION
Database name was -not- entered in the Save as database dialog with a leading
"/".
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the KMyMoney-devel
mailing list