eq.lootdrop_entries

Casai · #1 03-30-2005, 07:26 PM

also found this for those who feel comfortable with MySQL. Looks like 4.1 can be used after all.

Quote:

Originally Posted by RangerDown

There was a mistake in its primary key definition -- the same field being listed twice -- and mysql 4 doesn't like that.

The primary key definition for that table has been corrected and should show up in the Sourceforge on the next beta release. If you're keen with editing the SQL file you can go ahead and edit what you have to fix the error.

Go to the lines that read:

Code:

CREATE TABLE lootdrop_entries (
  lootdrop_id int(11) unsigned NOT NULL default '0',
  item_id int(11) NOT NULL default '0',
  item_charges tinyint(2) unsigned NOT NULL default '1',
  equip_item tinyint(2) unsigned NOT NULL default '0',
  chance tinyint(2) unsigned NOT NULL default '1',
  PRIMARY KEY  (lootdrop_id,item_id,lootdrop_id)
) TYPE=MyISAM;

Change that PRIMARY KEY line so that the lootdrop_id field is listed only once in it. Should then read:

Code:

  PRIMARY KEY  (lootdrop_id,item_id)