etan39
/
cloudstack
mirror of https://github.com/apache/cloudstack.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

db: Re-enable db foreign key checking at the end of the upgrade path 

Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
This commit is contained in:
Rohit Yadav 2013-02-26 12:32:21 +05:30
parent d37ed18c3a
commit 755ddc52d1
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
setup/db/db/schema-410to420.sql
View File

@ -19,6 +19,7 @@
-- Schema upgrade from 4.1.0 to 4.2.0;
--;
-- Disable foreign key checking
SET foreign_key_checks = 0;
ALTER TABLE `cloud`.`hypervisor_capabilities` ADD COLUMN `max_hosts_per_cluster` int unsigned DEFAULT NULL COMMENT 'Max. hosts in cluster supported by hypervisor';
@ -97,7 +98,6 @@ CREATE TABLE `vpc_service_map` (
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
SET foreign_key_checks = 1;
INSERT IGNORE INTO `cloud`.`configuration` VALUES ('Advanced', 'DEFAULT', 'management-server', 'vm.instancename.flag', 'false', 'Append guest VM display Name (if set) to the internal name of the VM');
@ -109,3 +109,6 @@ CREATE TABLE `cloud`.`user_vm_clone_setting` (
INSERT IGNORE INTO `cloud`.`configuration` VALUES ('Advanced', 'DEFAULT', 'UserVmManager', 'vmware.create.full.clone' , 'false', 'If set to true, creates VMs as full clones on ESX hypervisor');
-- Re-enable foreign key checking, at the end of the upgrade path
SET foreign_key_checks = 1;