Question about MYSQLX read & write
Hey, im again and im still on it...
I try to rewrite the sql funktion of the wowmod, because there is to much stuff to load, and read at one time! I ask me by the way what could be a better way to split the data of it! My first idea iss to handle the basic informations alone, like race, class, class1 and so on, because at this moment its all together in one column. But if we want to do some "fast" checks we have to use all of it, so there will be more information to load then needed. The problem for me is, i dont know whats better, to create for all informations a own table with own columns for things like "player_char" and "player_spells" or is it fast enough to split them in the existing table?! The example like it is atm for player data `data` TEXT NOT NULL: Code:
format( data, 512, "%d %d %d %d %d %d %d %d %d %d %d %d", Thanks by the way for any idea or suggestion! |
Re: Question about MYSQLX read & write
Would you format all that in one public funtion? or save every class with its abbilities in a diffrent function?
if you would save all that in one function then i pretty sure that you're way would require more cpu and get more peaks. also you need to think about how userfriendly managing you're tables on you're database would become from my expierence with my knifemod bits vaultsaving made by exolent, became buggy for alot of hosters, I myself had problems with it but that's becous of the skins saving method ut sometimes ppl would have upgrades that they didnt even buy. if you would change the saving and loading of the wow plugin then you have to edit everywhere where that function is called to make you're changes apply in the correct way depending on what needs to be saved so you would need to make checks for what races and abilities they just bought or etc (idk how wow mod works :p) |
| All times are GMT -4. The time now is 05:45. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.