vales
06-03-2009, 03:58 PM
Hey, CaveDude.
I was meaning to ask if you could update the PEQDB with additional SQL query updates instead of uploading the whole database. This way, it's much more efficient to keep modifications and is lighter on your resources. We're always updating the whole thing instead of sourcing in only the database updates. Not the updates like Rev610.sql in the updates folder, but rather the actual sql query just for the database like items, mobs, etc.
If you could just post the difference files as far as updates are concerned, then it would be much easier. ;)
The way I've learned to keep database updates in order was to have SQL entries from, for example, Rev10 to Rev20, was to post just the updates for those that already have Rev10 running, but post the sql data relevant up to Rev20.
This way, people can update it manually, source in additional tweaks and stuff without having to source in a completely full database before adding in updates again. Then, you could also have a full Rev20 for download for those that haven't used Rev10 yet. This way, it's much easier to also keep track of errenous files and issue a quickfix without breaking the whole database in the process or sourcing in the whole thing again when updating.
Breaking up the SQL files into categories would be ideal as well. For example, there's already sql entries for characters.sql, load_system.sql, etc. But in a Rev20 folder for example, there would be an item.sql that contained all of the item updates from Rev10 to Rev20, a mobs.sql that contained all of the mob updates, etc. This way, it's easier to pick and choose and also keep track of fixes much, much easier.
If people want to customize their servers without adding in let's say, adventure merchants, then they can immediately pick out what they don't want by commenting it out and then just sourcing in the rest. :-)
I was meaning to ask if you could update the PEQDB with additional SQL query updates instead of uploading the whole database. This way, it's much more efficient to keep modifications and is lighter on your resources. We're always updating the whole thing instead of sourcing in only the database updates. Not the updates like Rev610.sql in the updates folder, but rather the actual sql query just for the database like items, mobs, etc.
If you could just post the difference files as far as updates are concerned, then it would be much easier. ;)
The way I've learned to keep database updates in order was to have SQL entries from, for example, Rev10 to Rev20, was to post just the updates for those that already have Rev10 running, but post the sql data relevant up to Rev20.
This way, people can update it manually, source in additional tweaks and stuff without having to source in a completely full database before adding in updates again. Then, you could also have a full Rev20 for download for those that haven't used Rev10 yet. This way, it's much easier to also keep track of errenous files and issue a quickfix without breaking the whole database in the process or sourcing in the whole thing again when updating.
Breaking up the SQL files into categories would be ideal as well. For example, there's already sql entries for characters.sql, load_system.sql, etc. But in a Rev20 folder for example, there would be an item.sql that contained all of the item updates from Rev10 to Rev20, a mobs.sql that contained all of the mob updates, etc. This way, it's easier to pick and choose and also keep track of fixes much, much easier.
If people want to customize their servers without adding in let's say, adventure merchants, then they can immediately pick out what they don't want by commenting it out and then just sourcing in the rest. :-)