Just finished loading it up, and what can I say....

Excellent work Drawde!!

Just wanted to let you know all your hard work is appreciated :D

Drawde addon
 

I know perfectly what to do with db.sql.. i created the db, i did a "mysql eq <db.sql" and i got errors (in tradeskillrecipes)

i fixed them, dropped created and imported again db.sql, and was ok.

But sourgin reloaddb.sql, i got MANY errors, most of them where duplicate keys (in many tables) that i double checked looking into the .txt files (many). And some others errors where of wrong column count in some insert statements (when i got an error of this type, i formatted the insert that was givin the error, and the insert before that like in a excell sheet... and i saw that the row giving error had some more or less columns than the one before).

I don't know if you guys are getting duplicate keys from the .txt files, but THEY ARE THERE...
do you want an example?

so...
from the db.sql in the 44dr1.zip


<quote>
CREATE TABLE tradeskillrecipe (
id int(11) NOT NULL auto_increment,
tradeskill smallint(6) NOT NULL default '0',
skillneeded smallint(6) NOT NULL default '0',
trivial smallint(6) NOT NULL default '0',
product smallint(6) NOT NULL default '0',
product2 smallint(6) NOT NULL default '0',
failproduct smallint(6) NOT NULL default '0',
productcount smallint(6) NOT NULL default '0',
i1 smallint(6) NOT NULL default '0',
i2 smallint(6) NOT NULL default '0',
i3 smallint(6) NOT NULL default '0',
i4 smallint(6) NOT NULL default '0',
i5 smallint(6) NOT NULL default '0',
i6 smallint(6) NOT NULL default '0',
i7 smallint(6) NOT NULL default '0',
i8 smallint(6) NOT NULL default '0',
i9 smallint(6) NOT NULL default '0',
i10 smallint(6) NOT NULL default '0',
notes text,
PRIMARY KEY (id),
UNIQUE KEY id (id),
UNIQUE KEY name (product)
) TYPE=MyISAM;

--
-- Dumping data for table 'tradeskillrecipe'
--


INSERT INTO tradeskillrecipe VALUES (1,68,14,16600,16500,10015,0,0,0,0,0,0,0,0);
INSERT INTO tradeskillrecipe VALUES (2,68,14,14600,16504,10015,0,0,0,0,0,0,0,0);
INSERT INTO tradeskillrecipe VALUES (3,68,30,14628,16504,10020,0,0,0,0,0,0,0,0);
INSERT INTO tradeskillrecipe VALUES (4,68,30,16656,16500,10020,0,0,0,0,0,0,0,0);
</quote>

do the insert have the same number of columns than the create table?

in the loot.txt, one example:
<quote>
INSERT INTO lootdrop VALUES (427,'InvisibleMan');
INSERT INTO lootdrop VALUES (427,'InvisibleManCaster');
</quote>

that is a duplicate entry... there are many...

same, for example, in merchantlist.txt
<quote>
INSERT INTO merchantlist VALUES (5750,12,11611); # warhammer of divine grace
INSERT INTO merchantlist VALUES (5750,13,3737); # breastplate of the holy rite
</quote>

then, a mismatch from db.sql and starting_items.txt

db.sql
<quote>
CREATE TABLE starting_items (
id int(11) unsigned NOT NULL auto_increment,
race int(11) NOT NULL default '0',
class int(11) NOT NULL default '0',
itemid int(11) NOT NULL default '0',
gm tinyint(1) NOT NULL default '0',
PRIMARY KEY (id,race)
) TYPE=MyISAM;
</quote>
and starting_items.txt
<quote>
INSERT IGNORE INTO starting_items (race, class, deityid, zoneid, itemid, item_charges) VALUES
</quote>

so, i'm not stating that drawde is doing a bad work... never want to say that..
i'm only saying that many of those errors where present a long time ago, and are still here.

if drawde try to source those files himself, he can find and fix those problems (duplicate keys and wrong column count) in less than a hour, so nobody (including himself) will have to think about that anymore.

If drawde want, i can make those fix myseld and pass the fixes to him... the only problem is that i can change keys, or add columns, but i'll be never sure if my fixes are correct (wrong values added?)

Sorry for my long posting and for my bad english.
And thanks to drawde for his work (even if i yet have to see his work running on my machine).

Dump of Drawde's DB - complete, just source and go.
 

I loaded up Drawde's DB ( excellent work IMHO ), then dumped it to a single sql file that I then zipped to attatch here.
Should be very simple, unzip into mysql bin folder, then...
create a fresh DB and source, includes everything , shouldn't be any errors.
Use with EqEmu 4.4DR1 for best results.

updated DB with missing items and NPC magery turned on and the EXE's I'm using with it here-
http://forums.eqemu.net/viewtopic.php?t=6717

Great work Dawde, I love your db. It's very complete and fun to play in. Please ignore the whiners, I agree with Trump, the users should do a little leg work, it doesn't hurt. Hey who knows, if all the users learned sql a little more, maybe they can use their skills to get a job later.. hmm? Plus, they should read all the threads fully before posting.

My only problem with the response is that it came across as 'why dont you check your work and make sure ALL errors are corrected before you post something'

Drawde specifically mentioned, as I did that there were a couple of bugs, but other than that it worked great....

The problem seems to be that the wrong db.sql is being used.
Its really not his job to go and put everything together for you and make a full release, if you want to use his BETA database, then you should go to CVS on sourceforge and download the latest db.sql file, rather than complaining about the one he provided. CVS is freely available to everyone, so use it. Otherwise, we'll just cut CVS updates off completely, and not make anything available until a stable version is released so we dont have people whining about not being able to attatch an updated part A to an updated part B because they expect everything to be done for them. When I set up the Sourceforge CVS updates, thats exactly what I was afraid of in the 1st place.

As Drawde notes in his version, it's beta, and no offense, but he's been releasing them for well over a year now, and has always done a smash up job, so the 'why dont you test it' tone kind of got under my skin'

He did offer to help fix the errors in a later post, which I think would have been more apprioate in the first post. Messages of this sort are appreciated..

'Hey, noticed a bug, you need to modify X to Y and that will correct it, in fact, I modified it and pasted it here !'

as opposed to

'Hey, noticed a bug.. We dont you fix these things before you release them?'

Like I said, I'm sure that's not what was meant, but the tone of the message came across as rude.

It wasn't my intention... my problem is that i don't know english enough to explain what i think, in the way i think it.

I was only stating that if he, or me, or someone else, is going to fix those duplicate keys one time, we will not get those errors in the future. At the moment, every person that want to use the db has to fix it himself.

And there are some ppl that have no sql know how.

Drawde said that some of the duplicate entries are there on purpose cuz he's waiting for the engine support that allows the same item to be created via different trade recipes. He also said that for the final release, he will make the db as complete and error free as possible. I also personally don't see how the duplicate entries really effect any of the end users. So take it easy, go load up the db, fire up the emu and enjoy the game, and wait for Drawde's final release..... I know I'm looking forwards to it. Peace...

Its not a problem, don't worry about it a bit. We're just a big, happy global community around here :-) Except for the french...
We hate the french... Paglioni sounds Italian to me...

Thanks
 

Thanks a lot drawde and all db builder :p nice work!

That's true.. i'm italian... and we too hate the french.. or at least I hate them... they tend to think the are better than anyone else... :)

Congrats Drawde on getting your DB updated and released.

To people having having trouble loading the DB, go back and re-read Drawde's instructions and follow them. Also take a little time and read the mySQL documentation. Look up the error and fix it. Then send Drawde a polite message with the problem, file and line it is on, nad it's solution. He can then fix it for everyone for the next release. And don't bother him with the dupe tradeskill lines that are intentional.

For those complaining, go spend a year making your own DB and show us just how easy it is. :twisted:

Thanks for mentioning those bugs anyway, I've fixed some of them now.
However this DB addon is a beta and so isn't 100% complete or error free, plus it's very easy for errors to creep in in hand-typed data like the merchant lists and loot (the NPC and faction data is auto-generated, but even that can have errors when there are typos in the source file.

so, if you want i can help you... i'll find those errors and i'll report to you... then you can fix them in the way you want ( i noticed that some dupe key are really mistyped numbers, and in this case i'll send you the file already patched).

The only thing i need is your updated db, because we don't have a CVS for it, and i don't wont to fix errors you already fixed, or lose your recent changes :)

you can send it in my email (info@darkangel.net) or via icq 104459
i'll test it as quick as possible.

Hi, i run a server (Dexter's EQ Server) and i use other people's DB's and edit them a small amount. the small edits i do are very complicated.. i couldent imagine starting one from scratch. I consider Drawde and Telmet as gods for doing this. I am currently using Telmet's DB, which i have edited to make mobs attack, and cast, also added in some loot to some named mods(doomshade, rumblecrush, ect.) i have tested Drawde's DB and it is great! only reason im still using telmets as it has most the mobs in ALL zones. But i cant wait till drawde's is done, im looking forward to quests and easyer tradeskills and other things he has implanted. KEEP UP THE GOOD WORK GUYS!!

I love you Drawde
 

Your the best ;)

Thanks for your hard work!