aboutsummaryrefslogtreecommitdiff
path: root/sql/updates/characters
diff options
context:
space:
mode:
authorariel- <ariel-@users.noreply.github.com>2017-04-11 23:57:29 -0300
committerariel- <ariel-@users.noreply.github.com>2017-04-12 02:19:55 -0300
commit4c593f12caa162c1bfb831bdbed934bb39155ddb (patch)
tree57dfc52e6a0f38e2f9a1a382ea8722d6764e5505 /sql/updates/characters
parente32a4f26aaa51fba2647aeb8ef751dd398bc09d8 (diff)
Core/Instance: stop updating the instance resettimes based on creature respawns
- Rather update normal instance reset time to 2 hours after last creature kill - This fixes yet another integer overflow due to the possibility of having time_t max showing up - Also change respawntime and resettime fields to bigint on respawn/instance related tables - Start using prepared statements on the InstanceSaveMgr
Diffstat (limited to 'sql/updates/characters')
-rw-r--r--sql/updates/characters/3.3.5/2017_04_12_01_characters.sql4
1 files changed, 4 insertions, 0 deletions
diff --git a/sql/updates/characters/3.3.5/2017_04_12_01_characters.sql b/sql/updates/characters/3.3.5/2017_04_12_01_characters.sql
new file mode 100644
index 00000000000..ed5617d2750
--- /dev/null
+++ b/sql/updates/characters/3.3.5/2017_04_12_01_characters.sql
@@ -0,0 +1,4 @@
+ALTER TABLE `creature_respawn` CHANGE `respawnTime` `respawnTime` bigint(20) unsigned NOT NULL DEFAULT '0';
+ALTER TABLE `gameobject_respawn` CHANGE `respawnTime` `respawnTime` bigint(20) unsigned NOT NULL DEFAULT '0';
+ALTER TABLE `instance` CHANGE `resettime` `resettime` bigint(20) unsigned NOT NULL DEFAULT '0';
+ALTER TABLE `instance_reset` CHANGE `resettime` `resettime` bigint(20) unsigned NOT NULL DEFAULT '0';