CLOUDSTACK-1355: Don't check foreign key constraint during db upgrades

Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
This commit is contained in:
Rohit Yadav 2013-02-22 19:28:07 +05:30
parent 5f8a2ee9be
commit 54f7933f11
2 changed files with 7 additions and 0 deletions

View File

@ -20,6 +20,7 @@
--;
use cloud;
SET foreign_key_checks = 0;
alter table vm_template add size bigint unsigned;
alter table vm_template add state varchar(255);
@ -1653,3 +1654,5 @@ CREATE TABLE `cloud`.`baremetal_pxe_devices` (
`host_id` bigint unsigned DEFAULT NULL COMMENT 'host id coresponding to the external pxe device',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
SET foreign_key_checks = 1;

View File

@ -19,6 +19,7 @@
-- Schema upgrade from 4.1.0 to 4.2.0;
--;
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';
UPDATE `cloud`.`hypervisor_capabilities` SET `max_hosts_per_cluster`=32 WHERE `hypervisor_type`='VMware';
@ -81,3 +82,6 @@ ALTER TABLE `cloud`.`service_offering` ADD COLUMN `is_volatile` tinyint(1) unsig
ALTER TABLE `cloud`.`networks` ADD COLUMN `network_cidr` VARCHAR(18) COMMENT 'The network cidr for the isolated guest network which uses IP Reservation facility.For networks not using IP reservation, network_cidr is always null.';
ALTER TABLE `cloud`.`networks` CHANGE `cidr` `cidr` varchar(18) COMMENT 'CloudStack managed vms get IP address from cidr.In general this cidr also serves as the network CIDR. But in case IP reservation feature is being used by a Guest network, networkcidr is the Effective network CIDR for that network';
SET foreign_key_checks = 1;