current peq db, quests, and eq-EMU revisions

[strider51]

Hello,

As a first time user, I've downloaded the current source for all of these and compiled successfully.

I load up the world, and then spawn 5 zone.exe's.

I get to the char creation screen, make a char. All good.
I go to login to the world, and it says Zone Not Found because it's looking for 'animation' in the spawn2 table.

quick sanity check:
Are the trunk head revisions of Database, quests, and server source compatible?

Also, all of the wiki guides talk about matching the Release versions and making sure that the DB version is greater than the source version.

Well, the latest PEQ DB zip just says db_dump.sql, so I don't know the rev. (the actual svn rev is 54...)

Any help out there? And thanks for all of this source; you guys have done ALOT.

[lerxst2112]

You need to apply all required SQL updates past 1900 I believe. They are in the trunk\EQEmuServer\utils\sql\svn directory.

[strider51]

this makes alot of sense, I just discovered that directory. (I also noticed a recent spawn2 table update... withi this exact line:

ALTER TABLE `spawn2` ADD COLUMN `animation` TINYINT(3) UNSIGNED NOT NULL DEFAULT '0' AFTER `enabled`;

windows failed me, I did a search for the word "animation" find in files on the root, and it came up with nothing... (been getting this alot lately)

Thank you, i'll let you know how it goes.

[strider51]

OK making some further progress.
Now Zone.exe crashes, it looks like its crashing when it goes to load spells.

my spells_new DB table is empty. sound abnormal?

[Burningsoul]

Spells_new being empty is VERY adnormal. Did you have many errors while sourcing the db_dump.sql? Might have to suck it up and do a fresh DB source.

[strider51]

thanks for the help. is there anyway to get all the updates in 1 shot? I actually made a vb script to create a sourceAll.sql that list them in numerical order, but I still get some errors like

"Column does not exist".

I'm wondering if there is another preferred order.

Here's what Im doing:
I'm creating a database with the db_dump.sql
then I'm applying all updates in the updates folder of that repository
then I'm applying all of the updates in the server Source SVN repository: trunk\EQEmuServer\utils\sql\svn

I get tons of duplicate entry, column, unknown colum errors; and I'm executing these updates in numerical order.


EDIT: doing this in this order deletes your spells_new table......

[strider51]

FIXED:

All i had to do was listen to the original Directions:

Load the db_dump.sql
Then install updates, but ONLY the updates that are greater than 1900.


I now have a running private local server; pretty cool.

[strider51]

Additional Question here:

Is there any other way to determine what SQL updates are necessary to run?
It seems like the main.sql source file used to have a revision attached to it so you could see what you needed to run.

The new one is just db_dump.sql, but has no revision number, so is anyone supposed to know which updates they need ?

Update: I looked at revision history on the peqDatabase directory. KimmySprite removed the version labeled file on 5/18/2011 and replaced with incremental. I guess I dont understand the idea behind this?

[lerxst2112]

KLS gave us a snapshot of the most recent database as of that date without the benefit of the nifty tools that Cavedude used to provide them. Treat it as 1900 and apply any updates past that.

[killianado]

Thanks. This thread answered the questions I had about which scripts to run to have a current DB. I tried following the tutorials but they were a little outdated but are still helpful. I can see the learning curve scaring off some. This is such a great project though.

Does the db_dump.sql already contain the load_bots.sql script? I am sure it does contain the load_player.sql since it is mandatory but as we all know bots are not.

[strider51]

So I just created a refresh, and heres what I did to get to the latest and greatest DB.

db_dump.sql to start
then source load_bots
then source load_player

then you need to source the following from the serverSource/utils/sql/svn (the repo that has the server source)

1711_account_restricted_aa.sql (creates the creation_time column and solves the UNIX_TIMESTAMP() issue)

1723_required_sql_corruption.sql (I needed this to spawn bots)

Then I sourced everything from 1908 up to the last which is 1977. Some of these are optional, and you don't need them.



I have a "1977_wothbots_dump" that I now use to refresh my dev project, or to run comparison queries. If you're interested I can put it up somewhere for you. It's like 160 megs tho.

[killianado]

Thanks, strider51.

I was under the impression that the db_dump.sql already had the load_player, 1711 and 1723. Not that running them again would cause any issues.

I sourced db_dump.sql and then 1900+ as lerxst2112 suggested and I am up and running. I wish there were an official master list to refer to but I am not complaining with such an awesome project!

[louis1016]

Originally Posted by killianado

Thanks, strider51.

I was under the impression that the db_dump.sql already had the load_player, 1711 and 1723. Not that running them again would cause any issues.

I sourced db_dump.sql and then 1900+ as lerxst2112 suggested and I am up and running. I wish there were an official master list to refer to but I am not complaining with such an awesome project!

it definitely doesnt include update 1723 im not sure about others

[killianado]

Thank you. Now I am really not sure how to be "up to date". db_dump.sql has no version information and it is missing a "required" update 1723? nice

I originally tried to use the guide at http://www.eqemulator.org/forums/showthread.php?t=32980 but I did not understand if you start with peqdb_rev1751.sql, why do the updates start with 1711? I thought you only need the updates that are higher than what you start with. or is it if you start with 1751, then you need all 1700+ updates?

This answer would help me out.

[lerxst2112]

1751 was missing some of the player table updates, and Cavedude noted that in the SVN commit notes. Since it didn't include all of the updates you need to backtrack a little to get it working.

The current dump can be considered 1900 since that's a nice even number. It's a little different than the usual dumps because it was done manually instead of with the scripts that Cavedude used, but it is perfectly workable. KLS was kind enough to provide it as an interim update.

1723 is not included because that is a bot only update, bots are not included in the dump, and the files sourced in the load_bots.sql file do not have that update included.