tanelipe you can close it i have it in inis now
INIs is not fixing it. Keeping the connection alive / reseting it (to stay alive) is fixing it.Quote:
Connection.Close();
Connection.Open();
Well yes, but why cover up the problem when you can fix it? Lol
ini's is for people that dunno how to do sql it isn't a fix it is basically jerryriggin it because you dunno how to fix it properly.Quote:
Connection.Close();
Connection.Open();
Well yes, but why cover up the problem when you can fix it? Lol
Mine never drops sql enless my internet drops momentarily lol because i have sql and server running on 2 different boxes not local and the sql is on a remote dedi box.Quote:
INIs is not fixing it. Keeping the connection alive / reseting it (to stay alive) is fixing it.
But, I am sorry, I had this topic go off-topic by debating over MySQL and INIs/cover ups.
Epic.Quote:
ini's is for people that dunno how to do sql it isn't a fix it is basically jerryriggin it because you dunno how to fix it properly.
I don't like (My)SQL, So I use INI's I don't use it because I can't use it properly, hell I have Ulti and all of his servers have been MySQL based. :P
Mine never drops sql enless my internet drops momentarily lol because i have sql and server running on 2 different boxes not local and the sql is on a remote dedi box.
There isn't even a need to reset the connection if sql is done correctly the 1 connection will stay alive entire time server is up.