Selecting data from mysql using qt?
-
hmmm pretty strange, does /var/run/mysqld exits? if you try
sudo mkdir /var/run/mysqld
and then the
sudo ln -s /opt/lampp/var/mysql/mysql.sock /var/run/mysqld/mysqld.sock
Though restart should not delete the directory, but I can't imagine anything else at the moment.
-
Hmmm... /var/run will be clear on each start, so you have to do a directory and the symlink again. You can do it with a script.
Or get rid of the whole LAMPP setup and use the regular mysql package. Maybe it's possible to run two mysql parallel, but I don't recommend that, too confusing.
-
If the problems after restart persists, then I think it will be time to change socket parameter in my.cnf. configs are created for changing settings and I don't think it will harm any component in lampp, because if it would then 1) a special note must have been written somewhere and 2) it makes no sense to allow user to change this setting if it breaks lampp.
-
I don't know LAMPP, but I have seen similar packages, where the packager wanted to keep everything in /opt and for that reason all settings and installation directories were changed. It might be, that the apache or php is configured, to look for the socket in the /opt/lampp.
However, I looked around in the documentation, and I found setConnectOptions(..) which could be a good workaround. I think it should work like this:
db.setConnectOptions("UNIX_SOCKET=/opt/lampp/var/mysql/mysql.sock");
The only problem is, if you move the program to a different system, it won't work again, so you should make some lookups in the code, if the above is correct or not in the actual system (usually it won't be).
If this problem heads up more often (the distribution packagers change the socket location for fun), maybe it's good to implement a socket search function somewhere in QSqlDatabase::open().
-
I was reading last posts and wondered, what if doforumda changes the way of connecting to mysql server. I just noticed that you can connect via tcp or socket, and here socket, as I understand is unix domain socket. Connecting via tcp might eliminate the need for looking sock files.
UPD: just a little bit more words. Unix domain sockets limit communicating process to be within the same OS, which is not true in general. At least I think the original application is not for local usage only.
-
Yes, it must be possible to connect to 127.0.0.1:3306, though it will not work, as all mysql default configuration comes with "--skip-networking" option, for good reason. You don't want your sql server to be reachable directly from the outside. Ofcourse you can turn this off, but probably that's not the way.
I still find the above with the connect options better, like this:
@db.setConnectOptions("UNIX_SOCKET=/opt/lampp/var/mysql/mysql.sock");
if (!db.open()) {
db.setConnectOptions(); // clears the connect option string
}
if (!db.open()) ... some error handling@
