Created attachment 124607 [details] 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 "/".
Please update to a newer version (we are currently at 5.0.7). I believe this has been fixed in the meantime, but currently don't find the bug entry/source code commit. Please report back here.
Thanks Thomas, appreciate the update. I'm on the Cygwin release. Haven't attempted to compile anything under Cygwin/for KDE, but I might give it a try. Any tips or pointers appreciated.
Sorry, but Windows and Cygwin are not my area of expertise. Anyone else?
I no longer have an active Windows installation, so I haven't used Cygwin in over a year, but compiling is very much like on Linux. I don't remember any particular problems, and when necessary (after asking here) I always found the Cygwin mailing list very responsive and helpful.
Hey, guys. Thanks for the help. Surprisingly enough for a non-programmer, I was able to get it to compile cleanly, and the error is gone - database connectivity seems to be working fine with MySQL/MariaDB on Cygwin with version 5.0.7. Really appreciate your responses. I can confirm that this is resolved in 5.0.7. Updating status accordingly, feel free to adjust as needed if I don't get it right. Thanks again.
*** This bug has been marked as a duplicate of bug 397675 ***