DB svn vs Source svn

[nosfentora]

Just a question about the differences in the PEQ DB svn and the Source svn.
looking at the contents of the DB @ rev 13, the last entries are
Rev467.sql
Rev507.sql
Rev512.sql

looking at the Source svn contents @ rev 512, the last entries are
475_aa_actions.sql
500_spawn2_optimization.sql
503_bugs.sql

it's looking like there are 2 copies of the DB updates, which one is the correct one to use? Some are identical and some aren't.

if one were to use only the DB SVN SQL, then they would not get the aa_actions updates, as they're not in Rev507.sql or Rev512.sql

if one were to only use the Source SVN SQL then one doesn't get the new db_version table, nor the updated rev value, and i believe there are some other updates missing.

this being said, wouldn't it be wise to combine them into 1 so that when the db is pulled, everyone gets everything and it's always the same? Just my $0.02 that it would make missing something less likely and make maintenance that much easier.

(after having written all this, it dawned on me that it could be the differences in PEQ vs AXClassic, if so - tell me to stuff it)

[cavedude]

Both are OK to use, as they will get you to the same place. However, due to the differences you pointed out I don't suggest using both as some do. It's best to use one or the other to update you. Though, as you have noticed the PEQ SVN does have some added tables and such because that's what the project is, the database. The EQEmu code will only provide you with core updates and none of the fancy extras I often add.

AAs are in the system tables, not the player tables which is why you won't see them as updates. Those changes are already in the big gz file. If you look in the player_tables folder the update files will only effect those tables listed there, all other updates will already be in the content gz.

The difference in version number is simply due to the way that I update the DB SVN. I give the DB and any update file (if one is needed) the current version number of EQEmu when it is uploaded, not when the change was made. So, if you see the DB SVN has a higher version number than the last time changes were required for the EQEmu code, then you are safe in that you'll have all those updates.

[nosfentora]

Thanks CD,

I'm working on an automatic updater & compiler that downloads source updates, db updates and sources and compiles the new rev's when released - and was trying to figure out which set of updates to use.

If i were to apply both, in numerical order, say

Rev438
447_sof_startzone_rule
Rev461
463_altadv_vars
475_aa_actions
500_spawn2_optimizations
503_bugs
Rev507
Rev512

are there potential problems? (i haven't opened each of those files yet to do a comparison)

[cavedude]

Yeah, as I said you don't want to mix them, all of the updates will be doubled. You'll probably just get errors it'll skip past, but if new columns are added to the database, then it will add two columns. It's best to use either or. I try to make the PEQ updates as complete as possible, so that might be the better way to do it. The only problem is database changes that are made before PEQ is updated. Though, when the core code changes I usually try to update PEQ to match it.

[nosfentora]

Thanks CD - appreciate it.

And keep up the good work!

maybe i'll make my updating dependent on PEQ updates then.
Though then I'll be behind on new revs.... ahh the dielmas!
lol


I like how you're updating the db_version table now!