Quote:
|
Originally Posted by Trumpcard
I don't understand what can be wrong with his db.sql, it just sounds to me like you didnt know what to do with it. The db.sql does not go over the top of an existing database. If you didnt create a new database, and tried to lay in the new db.sql over the old one, no wonder you got a ton of errors. Thats a user error, not a problem in anything Drawde did. If you had dropped your original database, created a new one, source in the new db.sql, then applied the addon, you would have gotten nothing more than a couple of bugs in a couple of sql files (mostly dupe errors), which will be ignore with a mysql -f insert.
Just my 2 cents.
|
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).
Except for the french... 
Linear Mode
