Bonsai Posted February 18, 2014 Share Posted February 18, 2014 Hey Peeps, just a little question. Imagine there is a /stats command. Should executeSQLQuery be used to get the stats every time the command is used, or should the stats be stored in a table on player join and saved when he quits? Basically, is there any real disadvantage when using executeSQLQuery? So far I haven't notice any performance issue, I just wanna know if its problematic doing it like that. Bonsai Link to comment
Castillo Posted February 18, 2014 Share Posted February 18, 2014 I'm not sure if it would be such a big deal when using SQLite, but it is if you use MySQL. Link to comment
Bonsai Posted February 18, 2014 Author Share Posted February 18, 2014 I'm not sure if it would be such a big deal when using SQLite, but it is if you use MySQL. Oh right, sorry. Of course I'm not using MySQL Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now