SVN Discussion

[cavedude]

I was meaning to add an updates folder to the PEQ CVS for instances like this when the user tables change. If you do a full install, then you're set, but obviously those who don't wish to lose their toons need to manually update their DB.

For the new tables, all you need to do is look at the tables on the PEQ CVS, and compare them to your current db. Any that you are missing, source (that's why the user tables are split up on CVS - so you can source in individual ones if you wish) Yes, new additions to commands, variables, and rule_values are tacked on the end of those files.

For the changed tables (character_ for example was changed) check out the utils/sql/09252008.sql file on the source SVN first and look for the ALTER table queries. If it effects a table that has a file on PEQ CVS, then you need to source it. (As an example, the character_ alters need to be done, but the spawngroup one does not as that is included in the system part of the DB already) Once that is done, go through the changelog and look for alter queries that aren't in that big change file that you might have missed along the way.

I'm going to add an updates folder to PEQ CVS to help ease this in the future now.

[cubber]

Thanks for the update Cavedude, I figured that was my issue. I did look at those files you mentioned last night and thought that they may already have been added to the db. I ended up reverting back to my 1029 stable with bots and just updated to the newest stable bot source. So I will run with that until you release 1029d then I will attempt svn again. Do you think you will be merging your "updates" folder in the 1029d cvs?

[cavedude]

Well, you could run the 1129d system DB with the 1129 binaries. Any extra tables/columns will be ignored by the code. Nothing was removed or changed in the DB that will break the code, nor will be to maintain full compatibility with stock EQEmu. (The SVN should be considered experimental) That way, you'll still be able to use the content additions/fixes.

Yeah, I'll put all of the updates to get a DB current from as far back as the group change in one sql in the updates folder. I'll also make sure the file can be sourced even if some of the tables/columns exist without destroying anything. Look for that later today.

[cubber]

I figured that the db was backwards compatable thank you for confirming it, and thanks for the all the hard work you put into this project!

[Angelox]

I just made a core update with my PEQ database here, which is about a week old. You should be able to run it and keep your account/character info, although you will loose your bot data (you can back that up with GeorgeS tool).
Here's the Link (always back up first!)
You still need to run these sqls if you want to use todays SVN;

ALTER TABLE `zone` ADD column `shutdowndelay` bigint (16) unsigned NOT NULL default '5000';
INSERT INTO rule_values VALUES (1,'Zone:AutoShutdownDelay', 5000);

This update should give you all the new tables that are out except the keyring table, since people already are using it.

[cavedude]

Bots won't be lost provided they run the .bat file on CVS before dropping and sourcing the DB But, not to offend why post a link to the PEQ db? PEQ's CVS is up to date with SVN.

[KrackAdams]

Is there going to be more w/ Bots Revision to download or is the Revision 166 Win32 binaries w/ Bots Featured Server Bots the last one or do you need to update SVN w/ Revision201-bots or higher or does the Revisions come with the bot code already sorry for the question I'm a noob when it comes to the SVN system