Sending information to a Mysql table

[Eritey]

For example, say I in my game I have a player name and I want to be able to send their player name and score to a Mysql table to form a highscore results page. How would I go about doing this? Would the game interact with the table directly or would I connect to a php script which would interact with the Mysql table?

[Laurent]

What does it have to do with SFML?

[Eritey]

Well, As I've no idea how'd I go about doing it I wasn't sure if sfml was capable of doing it with its provided networking libraries. So I was just after some help with it, but if its the wrong place for this kinda of topic, feel free to close this topic.

[eXpl0it3r]

Using TCP/UPD and communicating with a MySQL server are two different things.
I mean sure you probably could implement the whole protocol for communicating with a MySQL server on top of TCP, but there are already libraries out there that do this. So you should probably Google a bit. If you're running a webserver anyway, you could think about implementing a PHP (or similar) script, which can be easily called with SFML's network module and then let the script talk to the database. It also gives you another layer of 'security' since you won't be talking to the database directly.

[io]

a long long time ago I can still remember how that... (ok I have a Don McLean song stuck in my head )

I used MySQL++ (http://tangentsoft.net/mysql++/) to wrap in SQL functionality into one of my projects; I would agree with exploiter though -- for 'safety' reasons and flexibility I'd probably communicate with a PHP script that handles the "heavy" work of the MySQL interface.

[hayer]

Soo you guys are saying he should create a PHP script and use that as a "proxy" between his MySQL server and C++ application?... That is just insane - to me at least.

If the application communicating with the MySQL server is a game server then you should use MySQL++ or any other C++ MySQL lib. Why? Since you control all the queries against the server and having some kind of PHP proxy just makes everything turn into syrup.

If the MySQL is meant for use client side, then your better of using something like SQLite3 or any other of the "locally stored"(or whatever you call them) database engines.

[eXpl0it3r]

Well you've read it the wrong way. It highly depends on the use-case. If you have to store a lot of stuff and talk to the database frequently it of course makes sense to use an existing library, but one should keep in mind that by doing so, one gives the application direct access to the database, which might get exploited. To kind of prevent that one could proxy everything over a PHP script or similar, thus only the server-sided script has direct access to the database and the application has a link to the script and you can make security checks on both ends. So if you use the server just to update some online highscore the later version seems to me more secure and thus I'd use it in that situation.