UPDATING your Database to be Compatible with the Latest Ascent Revisions menu

User Tag List

Page 1 of 4 1234 LastLast
Results 1 to 15 of 54
  1. #1
    JulianX's Avatar Contributor
    Reputation
    106
    Join Date
    Jun 2007
    Posts
    177
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    UPDATING your Database to be Compatible with the Latest Ascent Revisions

    Here is a Guide on making it so your Database is up to date with the Latest Ascent Revisions.

    This has all the Ascent Updates since Revision 736!


    Execute these in your SQL Command line in Navicat, SQLyog or any other MySQL GUI Program.

    SQL Updates for 736 940:
    World Database Updates:
    `creature_proto` UPDATE:
    Code:
    ALTER TABLE  `creature_proto` ADD COLUMN `money` INT (30) DEFAULT '0' NOT NULL  AFTER `boss`;
    SQL Updates for 941-1070:
    World Database Updates:
    `creature_staticspawns` TABLE:
    Code:
    CREATE TABLE `creature_staticspawns` (
     `id` int(30) NOT NULL AUTO_INCREMENT,
     `entry` int(30) NOT NULL,
     `map` int(11) NOT NULL DEFAULT '0',
     `x` float NOT NULL,
     `y` float NOT NULL,
     `z` float NOT NULL,
     `0` float NOT NULL,
     `movetype` int(11) NOT NULL DEFAULT '0',
     `displayid` int(11) NOT NULL,
     `factionid` int(11) NOT NULL DEFAULT '0',
     `flags` int(30) NOT NULL DEFAULT '0',
     `bytes` int(30) NOT NULL DEFAULT '0',
     `bytes2` int(30) NOT NULL DEFAULT '0',
     `emote_state` int(11) NOT NULL DEFAULT '0',
     `respawnNpcLink` int(11) NOT NULL DEFAULT '0',
     PRIMARY KEY (`id`)
    ) engine=innodb DEFAULT CHARSET=utf8;
    `gameobject_staticspawns` TABLE:
    Code:
    CREATE TABLE `gameobject_staticspawns` (
     `id` int(30) NOT NULL AUTO_INCREMENT,
     `entry` int(30) NOT NULL,
     `map` int(11) NOT NULL DEFAULT '0',
     `x` float NOT NULL,
     `y` float NOT NULL,
     `z` float NOT NULL,
     `facing` float NOT NULL,
     `0` float NOT NULL,
     `01` float NOT NULL,
     `02` float NOT NULL,
     `03` float NOT NULL,
     `state` int(11) NOT NULL DEFAULT '0',
     `flags` int(30) NOT NULL DEFAULT '0',
     `faction` int(11) NOT NULL DEFAULT '0',
     `scale` float NOT NULL,
     `respawnNpcLink` int(11) NOT NULL DEFAULT '0',
     PRIMARY KEY (`id`)
    ) engine=innodb DEFAULT CHARSET=utf8;
    `worldmap_info` TABLE UPDATE:
    Code:
    alter table worldmap_info add column required_quest int(30) not null default 0 after lvl_mod_a;
    alter table worldmap_info add column required_itemid int(30) not null default 0 after lvl_mod_a;
    SQL Updates for 1071-1131:
    World Database Updates:
    `fishingloot`,`creatureloot`,`objectloot`,`itemloot`,`pickpocketingloot`,`prospe ctingloot`,`skinningloot` TABLE UPDATES:
    Code:
    ALTER TABLE creatureloot DROP heroicchance;
    ALTER TABLE creatureloot DROP mincount;
    ALTER TABLE creatureloot DROP maxcount;
    
    ALTER TABLE fishingloot DROP heroicchance;
    ALTER TABLE fishingloot DROP mincount;
    ALTER TABLE fishingloot DROP maxcount;
    
    ALTER TABLE itemloot DROP heroicchance;
    ALTER TABLE itemloot DROP mincount;
    ALTER TABLE itemloot DROP maxcount;
    
    ALTER TABLE objectloot DROP heroicchance;
    ALTER TABLE objectloot DROP mincount;
    ALTER TABLE objectloot DROP maxcount;
    
    ALTER TABLE pickpocketingloot DROP heroicchance;
    ALTER TABLE pickpocketingloot DROP mincount;
    ALTER TABLE pickpocketingloot DROP maxcount;
    
    ALTER TABLE prospectingloot DROP heroicchance;
    ALTER TABLE prospectingloot DROP mincount;
    ALTER TABLE prospectingloot DROP maxcount;
    
    ALTER TABLE skinningloot DROP heroicchance;
    ALTER TABLE skinningloot DROP mincount;
    ALTER TABLE skinningloot DROP maxcount;
    
    ALTER TABLE creatureloot MODIFY column percentchance float(0) NOT NULL default 0;
    ALTER TABLE creatureloot ADD column heroicchance float(0) NOT NULL default 0 AFTER percentchance;
    ALTER TABLE creatureloot ADD column mincount int(30) NOT NULL default 1;
    ALTER TABLE creatureloot ADD column maxcount int(30) NOT NULL default 1;
    
    ALTER TABLE fishingloot MODIFY column percentchance float(0) NOT NULL default 0;
    ALTER TABLE fishingloot ADD column heroicchance float(0) NOT NULL default 0 AFTER percentchance;
    ALTER TABLE fishingloot ADD column mincount int(30) NOT NULL default 1;
    ALTER TABLE fishingloot ADD column maxcount int(30) NOT NULL default 1;
    
    ALTER TABLE itemloot MODIFY column percentchance float(0) NOT NULL default 0;
    ALTER TABLE itemloot ADD column heroicchance float(0) NOT NULL default 0 AFTER percentchance;
    ALTER TABLE itemloot ADD column mincount int(30) NOT NULL default 1;
    ALTER TABLE itemloot ADD column maxcount int(30) NOT NULL default 1;
    
    ALTER TABLE objectloot MODIFY column percentchance float(0) NOT NULL default 0;
    ALTER TABLE objectloot ADD column heroicchance float(0) NOT NULL default 0 AFTER percentchance;
    ALTER TABLE objectloot ADD column mincount int(30) NOT NULL default 1;
    ALTER TABLE objectloot ADD column maxcount int(30) NOT NULL default 1;
    
    ALTER TABLE pickpocketingloot MODIFY column percentchance float(0) NOT NULL default 0;
    ALTER TABLE pickpocketingloot ADD column heroicchance float(0) NOT NULL default 0 AFTER percentchance;
    ALTER TABLE pickpocketingloot ADD column mincount int(30) NOT NULL default 1;
    ALTER TABLE pickpocketingloot ADD column maxcount int(30) NOT NULL default 1;
    
    ALTER TABLE prospectingloot MODIFY column percentchance float(0) NOT NULL default 0;
    ALTER TABLE prospectingloot ADD column heroicchance float(0) NOT NULL default 0 AFTER percentchance;
    ALTER TABLE prospectingloot ADD column mincount int(30) NOT NULL default 1;
    ALTER TABLE prospectingloot ADD column maxcount int(30) NOT NULL default 1;
    
    ALTER TABLE skinningloot MODIFY column percentchance float(0) NOT NULL default 0;
    ALTER TABLE skinningloot ADD column heroicchance float(0) NOT NULL default 0 AFTER percentchance;
    ALTER TABLE skinningloot ADD column mincount int(30) NOT NULL default 1;
    ALTER TABLE skinningloot ADD column maxcount int(30) NOT NULL default 1;
    SQL Updates for 1132-1142:
    World Database Updates:
    `creature_proto` TABLE UPDATES:
    Code:
    alter table creature_proto change health minhealth int(30) unsigned not null;
    alter table creature_proto add column maxhealth int(30) unsigned not null after minhealth;
    update creature_proto set maxhealth=minhealth;
    alter table creature_proto change level minlevel int(30) unsigned not null;
    alter table creature_proto add column maxlevel int(30) unsigned not null after minlevel;
    update creature_proto set maxlevel=minlevel;
    alter table creature_proto add column invisibility_type int(30) unsigned not null;
    alter table creature_proto add column death_state int(30) unsigned not null;
    SQL Updates for 1143-1359:
    World Database Updates:
    `zoneguards` TABLE:
    Code:
    CREATE TABLE `zoneguards` (
      `zoneId` int(10) unsigned NOT NULL,
      `hordeEntry` int(10) unsigned default NULL,
      `allianceEntry` int(10) unsigned default NULL
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    SQL Updates for 1360-1381:
    Character Database Updates:
    `playerpets` TABLE UPDATE:
    NOTE: DELETES OLD `playerpets` TABLES.
    Code:
    DROP TABLE `playerpets`;
    
    CREATE TABLE `playerpets` (
      `ownerguid` bigint(20) NOT NULL default '0',
      `petnumber` int(11) NOT NULL default '0',
      `name` varchar(21) NOT NULL default '',
      `entryid` bigint(20) NOT NULL default '0',
      `data` longtext NOT NULL,
      `xp` int(11) NOT NULL default '0',
      `active` tinyint(1) NOT NULL default '0',
      `level` int(11) NOT NULL default '0',
      `happiness` int(11) NOT NULL default '0',
      `actionbar` varchar(200) NOT NULL default '',
      `happinessupdate` int(11) NOT NULL default '0',
      `summon` int(11) NOT NULL default '0',
      `autocastspell` int(11) NOT NULL default '0',
      `loyaltypts` int(11) NOT NULL default '0',
      `loyaltyupdate` int(11) NOT NULL default '0'
    ) engine=innodb DEFAULT CHARSET=latin1;
    SQL Updates for 1382-1392:
    Character Database Updates:
    `playeritem` TABLE UPDATES:
    NOTE: BACKUP CHAR DB BEFORE UPDATING.
    Code:
    alter table playeritems drop column guid;
    alter table playeritems add column guid bigint(10) NOT NULL auto_increment primary key after ownerguid;
    SQL Updates for 1393-1424:
    World Database Updates:
    `banned_names` TABLE:
    Code:
    CREATE TABLE `banned_names` (
      `name` varchar(30) NOT NULL
    ) engine=innodb DEFAULT CHARSET=latin1;
    SQL Updates for 1425-1471:
    `ai_agents` OPTIONAL TABLE UPDATE:
    Code:
    update ai_agents set spellCooldown=-1 where spellCooldown=0
    SQL Updates for 1472-1541:
    World Database Updates:
    `totemspells` TABLE UPDATES:
    Code:
    INSERT INTO totemspells (spellId, spellToCast1, spellToCast2, spellToCast3) VALUES (2894, 32982, 0, 0);
    INSERT INTO totemspells (spellId, spellToCast1, spellToCast2, spellToCast3) VALUES (2062, 33663, 0, 0);
    SQL Updates for 1542-1601:
    World Database Updates:
    `creature_proto` TABLE UPDATE:
    Code:
    ALTER TABLE creature_proto ADD walk_speed FLOAT DEFAULT "2.5" NOT NULL AFTER death_state;
    ALTER TABLE creature_proto ADD run_speed FLOAT DEFAULT "8" NOT NULL AFTER walk_speed;
    Character Database Updates:
    `arenateams` TABLE:
    Code:
    CREATE TABLE `arenateams` (
      `id` int(30) NOT NULL,
      `type` int(30) NOT NULL,
      `leader` int(30) NOT NULL,
      `name` varchar(150) NOT NULL,
      `emblemstyle` int(40) NOT NULL,
      `emblemcolour` bigint(40) NOT NULL,
      `borderstyle` int(40) NOT NULL,
      `bordercolour` bigint(40) NOT NULL,
      `backgroundcolour` bigint(40) NOT NULL,
      `rating` int(30) NOT NULL,
      `data` varchar(150) NOT NULL,
      `ranking` int(30) NOT NULL,
      `player_data1` varchar(60) NOT NULL,
      `player_data2` varchar(60) NOT NULL,
      `player_data3` varchar(60) NOT NULL,
      `player_data4` varchar(60) NOT NULL,
      `player_data5` varchar(60) NOT NULL,
      PRIMARY KEY  (`id`)
    ) engine=innodb DEFAULT CHARSET=latin1;

    `charters` TABLE:
    Code:
    CREATE TABLE `charters` (
      `charterId` int(30) NOT NULL,
      `charterType` int(30) NOT NULL default '0',
      `leaderGuid` int(20) unsigned NOT NULL default '0',
      `guildName` varchar(32) NOT NULL default '',
      `itemGuid` bigint(40) unsigned NOT NULL default '0',
      `signer1` int(10) unsigned NOT NULL default '0',
      `signer2` int(10) unsigned NOT NULL default '0',
      `signer3` int(10) unsigned NOT NULL default '0',
      `signer4` int(10) unsigned NOT NULL default '0',
      `signer5` int(10) unsigned NOT NULL default '0',
      `signer6` int(10) unsigned NOT NULL default '0',
      `signer7` int(10) unsigned NOT NULL default '0',
      `signer8` int(10) unsigned NOT NULL default '0',
      `signer9` int(10) unsigned NOT NULL default '0',
      PRIMARY KEY  (`charterId`),
      UNIQUE KEY `leaderGuid` (`leaderGuid`)
    ) engine=innodb DEFAULT CHARSET=latin1;
    SQL Updates for 1602-1729:
    Character Database Updates:
    `server_settings` TABLE:
    Code:
    CREATE TABLE `server_settings` (
      `setting_id` varchar(200) NOT NULL,
      `setting_value` int(50) NOT NULL,
      PRIMARY KEY  (`setting_id`)
    ) engine=innodb DEFAULT CHARSET=latin1;
    `characters` TABLE UPDATE:
    Code:
    alter table characters change lastDailyReset honorPointsToAdd INT(10) NOT NULL; 
    update characters set honorPointsToAdd = 0;
    alter table characters change charterId arenaPoints INT(10) NOT NULL;
    update characters set arenaPoints = 0;
    World Database Updates:
    `creature_names` TABLE UPDATE:
    Code:
    alter table creature_names change displayid male_displayid int(30) not null;
    alter table creature_names add column female_displayid int(30) not null after male_displayid;
    alter table creature_names add column unknown_int1 int(30) not null default 0 after female_displayid;
    alter table creature_names add column unknown_int2 int(30) not null default 0 after unknown_int1;
    alter table creature_names change unk2 unknown_float1 float(0) not null;
    alter table creature_names change unk3 unknown_float2 float(0) not null;
    alter table creature_proto add column fly_speed float(0) default "14.0" not null;
    alter table creature_proto add column extra_a9_flags int(30) default 0 not null;
    SQL Updates for 1730-1742:
    World Database Updates:
    `creature_spawns` TABLE UPDATE:
    Code:
    alter table creature_spawns add column channel_spell int(30) not null default 0;
    alter table creature_spawns add column channel_target_sqlid int(30) not null default 0;
    alter table creature_spawns add column channel_target_sqlid_creature int(30) not null default 0;
    SQL Updates for 1743-1785:
    World Database Updates:
    `spell_proc_data` TABLE:
    Code:
    CREATE TABLE `spell_proc_data` (
      `name_hash` int(30) NOT NULL,
      `proc_chance` int(30) NOT NULL,
      `forced_proc_flags` int(30) NOT NULL default '-1',
      PRIMARY KEY  (`name_hash`)
    ) engine=innodb DEFAULT CHARSET=latin1;
    SQL Updates for 1786-1836:
    Character Database Updates:
    `character` TABLE UPDATE:
    Code:
    alter table characters add column custom_faction int(30) default 0 not null after gender;
    SQL Updates for 1837-1843:
    World Database Updates:
    `trainer_defs` TABLE:
    Code:
    DROP TABLE IF EXISTS `trainer_defs`;
    CREATE TABLE `trainer_defs` (
      `entry` int(11) unsigned NOT NULL DEFAULT '0',
      `required_skill` int(11) unsigned NOT NULL DEFAULT '0',
      `required_skillvalue` int(11) unsigned DEFAULT '0',
      `req_class` int(11) unsigned NOT NULL DEFAULT '0',
      `trainer_type` int(11) unsigned NOT NULL DEFAULT '0',
      `trainer_ui_window_message` text,
      `can_train_gossip_textid` int(11) NOT NULL,
      `cannot_train_gossip_textid` int(11) NOT NULL,
      PRIMARY KEY (`entry`),
      UNIQUE KEY `entry` (`entry`),
      KEY `entry_2` (`entry`)
    ) engine=innodb DEFAULT CHARSET=utf8 COMMENT='Trainer System';
    `trainer_spells` TABLE:
    Code:
    DROP TABLE IF EXISTS `trainer_spells`;
    CREATE TABLE `trainer_spells` (
      `entry` int(11) unsigned NOT NULL DEFAULT '0',
      `cast_spell` int(11) unsigned NOT NULL DEFAULT '0',
      `spellcost` int(11) unsigned NOT NULL DEFAULT '0',
      `reqspell` int(11) unsigned NOT NULL DEFAULT '0',
      `reqskill` int(11) unsigned NOT NULL DEFAULT '0',
      `reqskillvalue` int(11) unsigned NOT NULL DEFAULT '0',
      `reqlevel` int(11) unsigned NOT NULL DEFAULT '0',
      `deletespell` int(11) unsigned NOT NULL DEFAULT '0',
      `is_prof` tinyint(1) unsigned NOT NULL DEFAULT '0',
      PRIMARY KEY (`entry`,`cast_spell`),
      KEY `entry` (`entry`)
    ) engine=innodb DEFAULT CHARSET=utf8 COMMENT='Trainer System';
    SQL Updates for 1844-1922:
    Character Database Updates:
    `playerpets` TABLE UPDATE:
    Code:
    ALTER TABLE playerpets DROP COLUMN autocastspell;
    UPDATE playerpets SET actionbar="";
    SQL Updates for 1923-2156:
    Character Database Updates:
    `playeritems` TABLE UPDATE:
    Code:
    alter table playeritems add column randomsuffix int(30) default 0 after randomprop;
    `instances` TABLE:
    Code:
    DROP TABLE IF EXISTS `instances`;
    SET @saved_cs_client     = @@character_set_client;
    SET character_set_client = utf8;
    CREATE TABLE `instances` (
      `id` int(30) NOT NULL,
      `mapid` int(30) NOT NULL,
      `creation` int(30) NOT NULL,
      `expiration` int(30) NOT NULL,
      `killed_npc_guids` text NOT NULL,
      `difficulty` int(30) NOT NULL,
      `creator_group` int(30) NOT NULL,
      `creator_guid` int(30) NOT NULL,
      PRIMARY KEY (`id`)
    ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
    SET character_set_client = @saved_cs_client;
    `accounts` TABLE UPDATES:
    Code:
    alter table accounts add column forceLanguage varchar(5) not null default "enUS";
    `playeritems_external` TABLE:
    Code:
    CREATE TABLE `playeritems_external` (
      `ownerguid` int(10) unsigned NOT NULL DEFAULT '0',
      `guid` bigint(20) unsigned NOT NULL DEFAULT '0',
      `entry` int(10) unsigned NOT NULL DEFAULT '0',
      `creator` int(10) unsigned NOT NULL DEFAULT '0',
      `count` int(10) unsigned NOT NULL DEFAULT '0',
      `charges` int(10) unsigned NOT NULL DEFAULT '0',
      `flags` int(10) unsigned NOT NULL DEFAULT '0',
      `randomprop` int(10) unsigned NOT NULL DEFAULT '0',
      `randomsuffix` int(30) NOT NULL,
      `itemtext` int(10) unsigned NOT NULL DEFAULT '0',
      `durability` int(10) unsigned NOT NULL DEFAULT '0',
      `containerslot` int(11) DEFAULT '-1' COMMENT '',
      `slot` tinyint(4) NOT NULL DEFAULT '0',
      `enchantments` longtext COLLATE utf8_unicode_ci NOT NULL,
      PRIMARY KEY (`guid`),
      UNIQUE KEY `guid` (`guid`),
      KEY `ownerguid` (`ownerguid`)
    ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
    `mailbox` TABLE UPDATES:
    Code:
    alter table mailbox add column external_attached_item_guid bigint(20) not null default 0 after attached_item_guid;
    SQL Empty Databases for 2157-2187:
    DOWNLOAD: Filebeam - Free Fast File Hosting

    SQL Updates for 2188-2191:
    World Database Updates:
    `worldmap_info` TABLE UPDATES:
    Code:
    UPDATE worldmap_info SET type=4 WHERE mapid IN (552, 554, 553, 540, 542, 543, 547, 546, 545, 560, 269, 556, 555, 557, 558 );
    ALTER TABLE `worldmap_info` ADD COLUMN `heroic_keyid_1` INTEGER(30) NOT NULL DEFAULT 0 AFTER `required_itemid`;
    ALTER TABLE `worldmap_info` ADD COLUMN `heroic_keyid_2` INTEGER(30) NOT NULL DEFAULT 0 AFTER `heroic_keyid_1`;
    UPDATE `worldmap_info` SET `heroic_keyid_1`=30633 WHERE `mapid` IN (555,556,557,558);
    UPDATE `worldmap_info` SET `heroic_keyid_1`=30634 WHERE `mapid` IN (552,553,554);
    UPDATE `worldmap_info` SET `heroic_keyid_1`=30635 WHERE `mapid` IN (269,560);
    UPDATE `worldmap_info` SET `heroic_keyid_1`=30623 WHERE `mapid` IN (545,546,547);
    UPDATE `worldmap_info` SET `heroic_keyid_1`=30637 WHERE `mapid` IN (540,542,543);
    UPDATE `worldmap_info` SET `heroic_keyid_2`=30622 WHERE `mapid` IN (540,542,543);
    SQL Updates for 2192-2271:
    World Database Updates:
    `quests` TABLE UPDATES:
    Code:
    ALTER TABLE `quests` ADD COLUMN `ReqCastSpellId1` INTEGER(11) NOT NULL DEFAULT 0 AFTER `ReqKillMobOrGOCount4`;
    ALTER TABLE `quests` ADD COLUMN `ReqCastSpellId2` INTEGER(11) NOT NULL DEFAULT 0 AFTER `ReqCastSpellId1`;
    ALTER TABLE `quests` ADD COLUMN `ReqCastSpellId3` INTEGER(11) NOT NULL DEFAULT 0 AFTER `ReqCastSpellId2`;
    ALTER TABLE `quests` ADD COLUMN `ReqCastSpellId4` INTEGER(11) NOT NULL DEFAULT 0 AFTER `ReqCastSpellId3`;
    Group Loot UPDATES:
    Code:
    ALTER TABLE `creatureloot` ADD COLUMN `ffa_loot` INTEGER UNSIGNED NOT NULL DEFAULT 0 AFTER `maxcount`;
     template function i surely dont want to make an exceptions, tho it may save some memory.
    ALTER TABLE `fishingloot` ADD COLUMN `ffa_loot` INTEGER UNSIGNED NOT NULL DEFAULT 0 AFTER `maxcount`;
    ALTER TABLE `itemloot` ADD COLUMN `ffa_loot` INTEGER UNSIGNED NOT NULL DEFAULT 0 AFTER `maxcount`;
    ALTER TABLE `pickpocketingloot` ADD COLUMN `ffa_loot` INTEGER UNSIGNED NOT NULL DEFAULT 0 AFTER `maxcount`;
    ALTER TABLE `prospectingloot` ADD COLUMN `ffa_loot` INTEGER UNSIGNED NOT NULL DEFAULT 0 AFTER `maxcount`;
    ALTER TABLE `skinningloot` ADD COLUMN `ffa_loot` INTEGER UNSIGNED NOT NULL DEFAULT 0 AFTER `maxcount`;
    ALTER TABLE `objectloot` ADD COLUMN `ffa_loot` INTEGER UNSIGNED NOT NULL DEFAULT 0 AFTER `maxcount`;
    SQL Updates for 2272-2289:
    Character Database Updates:
    `playeritems` TABLE UPDATES:
    Code:
    alter table playeritems add column wrapped_item_id int(30) not null default 0 after entry;
    alter table playeritems_external add column wrapped_item_id int(30) not null default 0 after entry;
    alter table playeritems add column wrapped_creator int(30) not null default 0 after wrapped_item_id;
    alter table playeritems_external add column wrapped_creator int(30) not null default 0 after wrapped_item_id;
    SQL Updates for 2290-2301:
    World Database Updates:
    `worldmap_info` TABLE UPDATES:
    Code:
    alter table worldmap_info add column viewingDistance float(0) not null default 80.0;
    SQL Updates for 2302-2310:
    Character Database Updates:
    `playeritems_insert_queue` TABLE:
    Code:
    DROP TABLE IF EXISTS `playeritems_insert_queue`;
    CREATE TABLE `playeritems_insert_queue` (
      `ownerguid` int(10) unsigned NOT NULL default '0',
      `entry` int(10) unsigned NOT NULL default '0',
      `wrapped_item_id` int(30) NOT NULL default '0',
      `wrapped_creator` int(30) NOT NULL default '0',
      `creator` int(10) unsigned NOT NULL default '0',
      `count` int(10) unsigned NOT NULL default '0',
      `charges` int(10) unsigned NOT NULL default '0',
      `flags` int(10) unsigned NOT NULL default '0',
      `randomprop` int(10) unsigned NOT NULL default '0',
      `randomsuffix` int(30) NOT NULL,
      `itemtext` int(10) unsigned NOT NULL default '0',
      `durability` int(10) unsigned NOT NULL default '0',
      `containerslot` int(11) NOT NULL default '-1' COMMENT 'couldnt find this being used in source',
      `slot` tinyint(4) NOT NULL default '0',
      `enchantments` longtext collate utf8_unicode_ci NOT NULL,
      KEY `ownerguid` (`ownerguid`)
    ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
    `characters_insert_queue` TABLE:
    Code:
    DROP TABLE IF EXISTS `characters_insert_queue`;
    CREATE TABLE `characters_insert_queue` (
      `insert_temp_guid` int(10) unsigned NOT NULL default '0',
      `acct` int(10) unsigned NOT NULL default '0',
      `name` varchar(21) collate utf8_unicode_ci NOT NULL,
      `race` tinyint(3) unsigned NOT NULL default '0',
      `class` tinyint(3) unsigned NOT NULL default '0',
      `gender` tinyint(3) unsigned NOT NULL default '0',
      `custom_faction` int(30) NOT NULL default '0',
      `level` int(10) unsigned NOT NULL default '0',
      `xp` int(10) unsigned NOT NULL default '0',
      `exploration_data` longtext collate utf8_unicode_ci NOT NULL,
      `skills` longtext collate utf8_unicode_ci NOT NULL,
      `watched_faction_index` int(10) unsigned NOT NULL default '0',
      `selected_pvp_title` int(10) unsigned NOT NULL default '0',
      `available_pvp_titles` int(10) unsigned NOT NULL default '0',
      `gold` int(10) unsigned NOT NULL default '0',
      `ammo_id` int(10) unsigned NOT NULL default '0',
      `available_prof_points` int(10) unsigned NOT NULL default '0',
      `available_talent_points` int(10) unsigned NOT NULL default '0',
      `current_hp` int(10) unsigned NOT NULL default '0',
      `current_power` int(10) unsigned NOT NULL default '0',
      `pvprank` tinyint(3) unsigned NOT NULL default '0',
      `bytes` int(10) unsigned NOT NULL default '0',
      `bytes2` int(10) unsigned NOT NULL default '0',
      `player_flags` int(10) unsigned NOT NULL default '0',
      `player_bytes` int(10) unsigned NOT NULL default '0',
      `positionX` float NOT NULL default '0',
      `positionY` float NOT NULL default '0',
      `positionZ` float NOT NULL default '0',
      `orientation` float NOT NULL default '0',
      `mapId` int(10) unsigned NOT NULL default '0',
      `zoneId` int(10) unsigned NOT NULL default '0',
      `taximask` longtext collate utf8_unicode_ci NOT NULL,
      `banned` int(40) NOT NULL,
      `banReason` varchar(50) collate utf8_unicode_ci NOT NULL,
      `timestamp` int(11) NOT NULL,
      `online` int(11) default NULL,
      `bindpositionX` float NOT NULL default '0',
      `bindpositionY` float NOT NULL default '0',
      `bindpositionZ` float NOT NULL default '0',
      `bindmapId` int(10) unsigned NOT NULL default '0',
      `bindzoneId` int(10) unsigned NOT NULL default '0',
      `isResting` tinyint(3) unsigned NOT NULL default '0',
      `restState` tinyint(3) unsigned NOT NULL default '0',
      `restTime` int(10) unsigned NOT NULL default '0',
      `playedtime` longtext collate utf8_unicode_ci NOT NULL,
      `deathstate` int(10) unsigned NOT NULL default '0',
      `TalentResetTimes` int(10) unsigned NOT NULL default '0',
      `first_login` tinyint(3) unsigned NOT NULL default '0',
      `forced_rename_pending` tinyint(3) unsigned NOT NULL default '0',
      `publicNote` varchar(32) collate utf8_unicode_ci NOT NULL,
      `officerNote` varchar(32) collate utf8_unicode_ci NOT NULL,
      `guildid` int(10) unsigned NOT NULL default '0',
      `guildRank` int(10) unsigned NOT NULL default '0',
      `arenaPoints` int(10) NOT NULL,
      `totalstableslots` int(10) unsigned NOT NULL default '0',
      `instance_id` int(10) unsigned NOT NULL default '0',
      `entrypointmap` int(10) unsigned NOT NULL default '0',
      `entrypointx` float NOT NULL default '0',
      `entrypointy` float NOT NULL default '0',
      `entrypointz` float NOT NULL default '0',
      `entrypointo` float NOT NULL default '0',
      `entrypointinstance` int(10) unsigned NOT NULL default '0',
      `taxi_path` int(10) unsigned NOT NULL default '0',
      `taxi_lastnode` int(10) unsigned NOT NULL default '0',
      `taxi_mountid` int(10) unsigned NOT NULL default '0',
      `transporter` int(10) unsigned NOT NULL default '0',
      `transporter_xdiff` float NOT NULL default '0',
      `transporter_ydiff` float NOT NULL default '0',
      `transporter_zdiff` float NOT NULL default '0',
      `spells` longtext collate utf8_unicode_ci NOT NULL,
      `deleted_spells` longtext collate utf8_unicode_ci NOT NULL,
      `reputation` longtext collate utf8_unicode_ci NOT NULL,
      `actions` longtext collate utf8_unicode_ci NOT NULL,
      `auras` longtext collate utf8_unicode_ci NOT NULL,
      `finished_quests` longtext collate utf8_unicode_ci NOT NULL,
      `honorPointsToAdd` int(10) NOT NULL,
      `killsToday` int(10) unsigned NOT NULL default '0',
      `killsYesterday` int(10) unsigned NOT NULL default '0',
      `killsLifeTime` int(10) unsigned NOT NULL default '0',
      `honorToday` int(10) unsigned NOT NULL default '0',
      `honorYesterday` int(10) unsigned NOT NULL default '0',
      `honorPoints` int(10) unsigned NOT NULL default '0',
      `difficulty` int(10) unsigned NOT NULL default '0',
      UNIQUE KEY `guid` (`insert_temp_guid`),
      KEY `acct` (`acct`),
      KEY `guildid` (`guildid`)
    ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
    SQL Updates for 2311-2319:
    Execute this file in your World DB
    DOWNLOAD: Filebeam - Free Fast File Hosting


    SQL Updates for 2320-2367:
    World Database Updates:
    `creature_names` TABLE UPDATE:
    Code:
    alter table creature_names add column mouseFlags int(30) not null default 0 after subname;
    `items` TABLE UPDATES:
    Code:
    alter table items add column ArenaRankRequirement int(30) not null default 0 after ItemExtendedCost;
    Character Database Updates:
    `guilds_ranks` TABLE UPDATES:
    Code:
    alter table guild_ranks add column rankRights_1 int(30) not null default 0;
    alter table guild_ranks add column rankRights_2 int(30) not null default 0;
    alter table guild_ranks add column rankRights_3 int(30) not null default 0;
    alter table guild_ranks add column rankRights_4 int(30) not null default 0;
    alter table guild_ranks add column rankRights_5 int(30) not null default 0;
    alter table guild_ranks add column rankRights_6 int(30) not null default 0;
    alter table guild_ranks add column rankRights_7 int(30) not null default 0;
    alter table guild_ranks add column rankRights_8 int(30) not null default 0;
    alter table guild_ranks add column rankRights_9 int(30) not null default 0;
    alter table guild_ranks add column rankRights_10 int(30) not null default 0;
    alter table guild_ranks add column rankRights_11 int(30) not null default 0;
    alter table guild_ranks add column rankRights_12 int(30) not null default 0;
    alter table guild_ranks add column rankRights_13 int(30) not null default 0;
    SQL Updates for 2368-2516:
    `worldmap_info` TABLE UPDATES:
    Code:
    alter table worldmap_info add column required_checkpoint int(30) not null default 0;
    `map_checkpoint` TABLE:
    Code:
    DROP TABLE IF EXISTS `map_checkpoint`;
    CREATE TABLE `map_checkpoint` (
      `entry` int(30) NOT NULL,
      `prereq_checkpoint_id` int(30) NOT NULL,
      `creature_id` int(30) NOT NULL,
      `name` varchar(255) NOT NULL,
      PRIMARY KEY  (`entry`)
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    Character Database Updates:
    `guild_checkpoints` TABLE:
    Code:
    DROP TABLE IF EXISTS `guild_checkpoints`;
    CREATE TABLE `guild_checkpoints` (
      `guildid` int(30) NOT NULL,
      `checkid` int(30) NOT NULL,
      PRIMARY KEY  (`guildid`,`checkid`)
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    SQL Updates for 2517-2528:
    World Database Updates:
    `creature_names` TABLE UPDATES:
    Code:
    ALTER TABLE creature_names CHANGE mouseFlags info_str VARCHAR(500) NOT NULL
    Character Database Updates:
    `character` TABLE UPDATE:
    Code:
    alter table characters drop column guildid;
    alter table characters drop column guildRank;
    alter table characters drop column publicNote;
    alter table characters drop column officerNote;
    alter table guilds modify column createdate int(30) not null default 0;
    `guild_logs` TABLE:
    Code:
    CREATE TABLE `guild_logs` (
      `log_id` int(30) NOT NULL,
      `guildid` int(30) NOT NULL,
      `timestamp` int(30) NOT NULL,
      `event_type` int(30) NOT NULL,
      `misc1` int(30) NOT NULL,
      `misc2` int(30) NOT NULL,
      `misc3` int(30) NOT NULL
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    `guild_data` TABLE:
    Code:
    CREATE TABLE `guild_data` (
      `guildid` int(30) NOT NULL,
      `playerid` int(30) NOT NULL,
      `guildRank` int(30) NOT NULL,
      `publicNote` varchar(300) NOT NULL,
      `officerNote` varchar(300) NOT NULL
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    `account_data` TABLE:
    Code:
    DROP TABLE IF EXISTS `account_data`;
    CREATE TABLE `account_data` (
      `acct` int(30) NOT NULL,
      `accountdata0` text NOT NULL,
      `accountdata1` text NOT NULL,
      `accountdata2` text NOT NULL,
      `accountdata3` text NOT NULL,
      `accountdata4` text NOT NULL,
      `accountdata5` text NOT NULL,
      `accountdata6` text NOT NULL,
      `accountdata7` text NOT NULL,
      PRIMARY KEY (`acct`)
    ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
    `playerpets` TABLE UPDATES:
    Code:
    ALTER TABLE `playerpets` CHANGE `entryId` `entry` int(10) unsigned NOT NULL DEFAULT '0';
    ALTER TABLE `playerpets` CHANGE `data` `fields` longtext COLLATE utf8_unicode_ci NOT NULL;
    ALTER TABLE `playerpets` DROP COLUMN `autocastspell`;
    Cumulative SQL Updates from 1561-2557:
    DOWNLOAD: Filebeam - Free Fast File Hosting

    SQL Updates for 2558+:
    Character Database Updates:
    `guilds` TABLE UPDATES:
    Code:
    alter table guilds add column bankBalance int(30) default 0 not null;
    alter table guilds drop guildbank_Tabs;
    `guild_bankitems` TABLE
    Code:
    CREATE TABLE `guild_bankitems` (
      `guildId` int(30) NOT NULL,
      `tabId` int(30) NOT NULL,
      `slotId` int(30) NOT NULL,
      `itemGuid` int(30) NOT NULL,
      PRIMARY KEY (`guildId`,`tabId`,`slotId`),
      KEY `a` (`guildId`),
      KEY `b` (`tabId`),
      KEY `c` (`slotId`)
    );
    `guild_banktabs` TABLE:
    Code:
    CREATE TABLE `guild_banktabs` (
      `guildId` int(30) NOT NULL,
      `tabId` int(30) NOT NULL,
      `tabName` varchar(200) NOT NULL,
      `tabIcon` varchar(200) NOT NULL,
      PRIMARY KEY (`guildId`,`tabId`),
      KEY `a` (`guildId`),
      KEY `b` (`tabId`)
    Enjoy,
    Julianx

    Last edited by JulianX; 12-21-2007 at 12:34 AM.

    UPDATING your Database to be Compatible with the Latest Ascent Revisions
  2. #2
    Mesmoras's Avatar Active Member
    Reputation
    30
    Join Date
    Jul 2007
    Posts
    332
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    If it's the latest revision, will it still work w/ your repack?
    +rep is a better way to thank some one.
    xxtennisdudexx: erm, u do know manGOS is VERY buggy compared to antrix.
    mesmoras: It may be buggy but it's so easy, even a caveman can do it. lol

  3. #3
    JulianX's Avatar Contributor
    Reputation
    106
    Join Date
    Jun 2007
    Posts
    177
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    yes if you use the updates for over 1143+

  4. #4
    Mesmoras's Avatar Active Member
    Reputation
    30
    Join Date
    Jul 2007
    Posts
    332
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    Nice. Do I have to update revision by revision? Or just execute the latest revision?
    +rep is a better way to thank some one.
    xxtennisdudexx: erm, u do know manGOS is VERY buggy compared to antrix.
    mesmoras: It may be buggy but it's so easy, even a caveman can do it. lol

  5. #5
    JulianX's Avatar Contributor
    Reputation
    106
    Join Date
    Jun 2007
    Posts
    177
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    Just use these updates and it will wrk with the latest revisions.

  6. #6
    Mesmoras's Avatar Active Member
    Reputation
    30
    Join Date
    Jul 2007
    Posts
    332
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    Oh your repack was rev 1220. So if I used all of the updates, even the ones before 1220, would it still be fine or would that just make it all go to hell?
    +rep is a better way to thank some one.
    xxtennisdudexx: erm, u do know manGOS is VERY buggy compared to antrix.
    mesmoras: It may be buggy but it's so easy, even a caveman can do it. lol

  7. #7
    JulianX's Avatar Contributor
    Reputation
    106
    Join Date
    Jun 2007
    Posts
    177
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    My repack was 1220 but it was only updated to 1143+ so use Updates 4-6

  8. #8
    SonicPT's Avatar Member
    Reputation
    1
    Join Date
    Aug 2007
    Posts
    4
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    I have rev 1016... How i update?

  9. #9
    megalord20's Avatar Member
    Reputation
    3
    Join Date
    Apr 2007
    Posts
    25
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    where do we put these

  10. #10
    Dragut's Avatar Member
    Reputation
    4
    Join Date
    Aug 2007
    Posts
    110
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    Could you tell us what all these updates do?

  11. #11
    Mesmoras's Avatar Active Member
    Reputation
    30
    Join Date
    Jul 2007
    Posts
    332
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    the update your db to be the latest revision...
    +rep is a better way to thank some one.
    xxtennisdudexx: erm, u do know manGOS is VERY buggy compared to antrix.
    mesmoras: It may be buggy but it's so easy, even a caveman can do it. lol

  12. #12
    JulianX's Avatar Contributor
    Reputation
    106
    Join Date
    Jun 2007
    Posts
    177
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    Added a new Update!

  13. #13
    Ragnaros's Avatar Member
    Reputation
    1
    Join Date
    May 2007
    Posts
    66
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    how do i update?

  14. #14
    Mesmoras's Avatar Active Member
    Reputation
    30
    Join Date
    Jul 2007
    Posts
    332
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    These updates are to be executed in your SQLyog/Navicat.
    +rep is a better way to thank some one.
    xxtennisdudexx: erm, u do know manGOS is VERY buggy compared to antrix.
    mesmoras: It may be buggy but it's so easy, even a caveman can do it. lol

  15. #15
    Ragnaros's Avatar Member
    Reputation
    1
    Join Date
    May 2007
    Posts
    66
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: UPDATING your Database to be Compatible with the Latest Ascent Revisions

    Yes? but its just a code? a line? how do i execute a text line in to SQLyog?

Page 1 of 4 1234 LastLast

Similar Threads

  1. [How-To] raise your home faction's reputation with the argent tournament
    By pangloss in forum World of Warcraft Guides
    Replies: 2
    Last Post: 06-05-2010, 07:45 AM
  2. [Question] Is there a way to have Nibbit compatable with the latest expansion/patch?
    By DavidTwo2009 in forum WoW ME Questions and Requests
    Replies: 8
    Last Post: 09-05-2009, 07:41 PM
  3. [ Updated Release ] CIDS Tier 7 (Compatible with the newest DBs)
    By God-Of-War in forum World of Warcraft Emulator Servers
    Replies: 2
    Last Post: 07-09-2008, 05:21 AM
  4. Replies: 2
    Last Post: 01-25-2008, 01:12 PM
All times are GMT -5. The time now is 08:58 AM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search