DB Tables Optimization
Reconsidered the use of MyISAM. Due to the old nature of the version of MySQL being used (5.1), the use of MyISAM on ROM-like tables makes it optimal since the table locks occurs only upon write. Added indexes on several tables, thus improving data reading by queries.
This commit is contained in:
@@ -19884,8 +19884,9 @@ USE `maplesolaxia`;
|
||||
`chance` int(11) NOT NULL DEFAULT '0',
|
||||
PRIMARY KEY (`id`),
|
||||
UNIQUE KEY (`dropperid`, `itemid`),
|
||||
KEY `mobid` (`dropperid`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
|
||||
KEY `mobid` (`dropperid`),
|
||||
INDEX (dropperid, itemid)
|
||||
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
|
||||
|
||||
#pass (sorted) data from one table to another
|
||||
INSERT INTO drop_data (dropperid, itemid, minimum_quantity, maximum_quantity, questid, chance)
|
||||
@@ -21223,7 +21224,7 @@ USE `maplesolaxia`;
|
||||
`mobid` int(11) NOT NULL DEFAULT '0',
|
||||
PRIMARY KEY (`id`) USING BTREE,
|
||||
UNIQUE KEY `id` (`id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
|
||||
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
|
||||
|
||||
INSERT INTO `monstercarddata` (`cardid`, `mobid`) (SELECT itemid, min(dropperid) FROM drop_data where itemid>=2380000 and itemid<2390000 group by itemid);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user