ini/sql

is right that if you switch from mysql to ini your server gets more stable??? cuz it won't loose that connection thing between server & database?
Or is just waste of time to switch to ini?
:handsdown:

for people that don't know what they're doing, id say yes, since you'd wouldn't be vulnerable to SQL exploits & injections and SQL exceptions in the server.

Well im not gonna do it, i just wanted know, im changing the sockets and i made auto backup every XX:50, so the server won't crash, cuz is used to crash when the server been up around 1hour ^^

Quote:

Originally Posted by ChingChong23 for people that don't know what they're doing, id say yes, since you'd wouldn't be vulnerable to SQL exploits & injections and SQL exceptions in the server.

the only reason your vulnerable to sql exploits and injections is because there is a error in your sql format... stop saying ini is better.

Quote:

Originally Posted by PeTe Ninja the only reason your vulnerable to sql exploits and injections is because there is a error in your sql format... stop saying ini is better.

I would say sql is better and easier to use with management for database etc. But ini is just quick setup in some cases what ever.
I would rather like to manage a sql database, then an ini database sine i got no experience with ini XD

Quote:

Originally Posted by PeTe Ninja the only reason your vulnerable to sql exploits and injections is because there is a error in your sql format... stop saying ini is better.

remember the people were dealing with here, nothing can go wrong using flat-file, having the sql causes more problems for people that don't know what they're doing. normally i suggest using sql, but in his case flatfile will be fine.

His source is vulnerable to SQL injection anyway.

Quote:

Originally Posted by PeTe Ninja the only reason your vulnerable to sql exploits and injections is because there is a error in your sql format... stop saying ini is better.

Carefull with what you're saying, do you want to imply mysql is better?

Quote:

Originally Posted by ChingChong23 remember the people were dealing with here, nothing can go wrong using flat-file, having the sql causes more problems for people that don't know what they're doing. normally i suggest using sql, but in his case flatfile will be fine. His source is vulnerable to SQL injection anyway.

I know what im doing, just asked ^^ to be sure if i should change XD
:) But im cool with sql at the moment as i fixed some troubles ^^ but just wanted to know if there was errors in ini and so XD
So ty ;D

Quote:

Originally Posted by ImmuneOne Carefull with what you're saying, do you want to imply mysql is better?

nope im just implying that they are equal :)

some have better benefits but still equal.

Quote:

Originally Posted by grillmad is right that if you switch from mysql to ini your server gets more stable??? cuz it won't loose that connection thing between server & database? Or is just waste of time to switch to ini? :handsdown:

Only reason why the MySQL connection would die/close is because the server is not using it correctly.

Quote:

Originally Posted by LetterX Only reason why the MySQL connection would die/close is because the server is not using it correctly.

True;)

Quote:

Originally Posted by LetterX Only reason why the MySQL connection would die/close is because the server is not using it correctly.

That is not the only reason.

Quote:

Originally Posted by Viscount S That is not the only reason.

Atually, the way the connection should be used is that its opened, makes 1 query and then closes again, theres no requirement for the connection to be kept open while its not being used, so the connection should never really be open long enough for it to die, because the server should close it when its finshed with it.

Quote:

Originally Posted by Korvacs Atually, the way the connection should be used is that its opened, makes 1 query and then closes again, theres no requirement for the connection to be kept open while its not being used, so the connection should never really be open long enough for it to die, because the server should close it when its finshed with it.

You're right, and with the quick connection time that the MySQL servers (and most likely others) have, speed shouldn't be an issue, but if you create a new connection every time a thread needs one, isn't that adding overhead in terms of (wasteful) resource usage, and unpredictable behavior under load?

That's what I've gathered by looking into connection pooling (which may or may not be useful in the context of a CO2 PServer) [Only registered and activated users can see links. Click Here To Register...].

Quote:

Originally Posted by Viscount S You're right, and with the quick connection time that the MySQL servers (and most likely others) have, speed shouldn't be an issue, but if you create a new connection every time a thread needs one, isn't that adding overhead in terms of (wasteful) resource usage, and unpredictable behavior under load? That's what I've gathered by looking into connection pooling (which may or may not be useful in the context of a CO2 PServer) [Only registered and activated users can see links. Click Here To Register...].

I have a single thread which deals with all database queries and the connection itself, so there isnt really an issue there for me.