Im not sure you are applying the updates properly. Now there are several methods to update the sqls, but I think first you want to know why you are updating them.. So long boring wall of text explanation follows:
Peq, one of the databases commonly used for the emulator, will hold all the structures required by the core to work properly, as well peq database holds all the spawn/creature info. When peq releases a database, they will label it with a number that relates to the latest core it was made for. As I write this that would be peqdb_rev1667.sql. This means that all the sql for the "core" up to 1667 are applied, as well as any changes peq has for spawns/creatures, ect..
EQemulator is in a constantly evolving state, changes are sometimes made to the way the database and core interact with each other and this will require an sql update to "an existing database", in this case if you applied the peq_rev1667 database, but then decided to update your emulator, or core, to say the latest binary release of 1708, then any sql's numbering above 1667 would need to be applied, unless they state "optional" of course. For this example these would be 1696_modify_zone_and_object_tables.sql as this sql falls between the last version of your peq db, 1667, and the current version of your core, 1708....
To get a better appreciation of the process it would be better to pull the source yourself and recompile whenever a dev releases a new push, which would require an sql update if one was pushed with that version. The reality is most people just use the precompiled binaries, but you should still understand the process nonetheless.
Eventually, peq will update to a newer version, and they will have incorporated all the sql updates that were released between their last db and the new one they are releasing..
|
Threaded Mode
