
Cinder SQL scripts assume too much about the environment and the way in which they are executed by sqlalchemy-migrate. Particularly, they manage transactions on their own even though sqlalchemy-migrate do it itself, plus it assumes that scripts are executed in one go (even though standard Python DB-API 2.0 does not mention multi-statement SQL commands to be executed on DB cursors. blueprint enable-mysql-connector Change-Id: I10c58b3af75d3ab9153a8bbd2a539bf1577de328 Closes-Bug: 1368391
122 lines
2.8 KiB
SQL
122 lines
2.8 KiB
SQL
CREATE TEMPORARY TABLE volumes_backup (
|
|
created_at DATETIME,
|
|
updated_at DATETIME,
|
|
deleted_at DATETIME,
|
|
deleted BOOLEAN,
|
|
id VARCHAR(36) NOT NULL,
|
|
ec2_id VARCHAR(255),
|
|
user_id VARCHAR(255),
|
|
project_id VARCHAR(255),
|
|
host VARCHAR(255),
|
|
size INTEGER,
|
|
availability_zone VARCHAR(255),
|
|
instance_uuid VARCHAR(36),
|
|
mountpoint VARCHAR(255),
|
|
attach_time VARCHAR(255),
|
|
status VARCHAR(255),
|
|
attach_status VARCHAR(255),
|
|
scheduled_at DATETIME,
|
|
launched_at DATETIME,
|
|
terminated_at DATETIME,
|
|
display_name VARCHAR(255),
|
|
display_description VARCHAR(255),
|
|
provider_location VARCHAR(256),
|
|
provider_auth VARCHAR(256),
|
|
snapshot_id VARCHAR(36),
|
|
volume_type_id VARCHAR(36),
|
|
source_volid VARCHAR(36),
|
|
PRIMARY KEY (id),
|
|
CHECK (deleted IN (0, 1))
|
|
);
|
|
|
|
INSERT INTO volumes_backup
|
|
SELECT created_at,
|
|
updated_at,
|
|
deleted_at,
|
|
deleted,
|
|
id,
|
|
ec2_id,
|
|
user_id,
|
|
project_id,
|
|
host,
|
|
size,
|
|
availability_zone,
|
|
instance_uuid,
|
|
mountpoint,
|
|
attach_time,
|
|
status,
|
|
attach_status,
|
|
scheduled_at,
|
|
launched_at,
|
|
terminated_at,
|
|
display_name,
|
|
display_description,
|
|
provider_location,
|
|
provider_auth,
|
|
snapshot_id,
|
|
volume_type_id,
|
|
source_volid
|
|
FROM volumes;
|
|
|
|
DROP TABLE volumes;
|
|
|
|
CREATE TABLE volumes (
|
|
created_at DATETIME,
|
|
updated_at DATETIME,
|
|
deleted_at DATETIME,
|
|
deleted BOOLEAN,
|
|
id VARCHAR(36) NOT NULL,
|
|
ec2_id VARCHAR(255),
|
|
user_id VARCHAR(255),
|
|
project_id VARCHAR(255),
|
|
host VARCHAR(255),
|
|
size INTEGER,
|
|
availability_zone VARCHAR(255),
|
|
instance_uuid VARCHAR(36),
|
|
mountpoint VARCHAR(255),
|
|
attach_time VARCHAR(255),
|
|
status VARCHAR(255),
|
|
attach_status VARCHAR(255),
|
|
scheduled_at DATETIME,
|
|
launched_at DATETIME,
|
|
terminated_at DATETIME,
|
|
display_name VARCHAR(255),
|
|
display_description VARCHAR(255),
|
|
provider_location VARCHAR(256),
|
|
provider_auth VARCHAR(256),
|
|
snapshot_id VARCHAR(36),
|
|
volume_type_id VARCHAR(36),
|
|
PRIMARY KEY (id),
|
|
CHECK (deleted IN (0, 1))
|
|
);
|
|
|
|
INSERT INTO volumes
|
|
SELECT created_at,
|
|
updated_at,
|
|
deleted_at,
|
|
deleted,
|
|
id,
|
|
ec2_id,
|
|
user_id,
|
|
project_id,
|
|
host,
|
|
size,
|
|
availability_zone,
|
|
instance_uuid,
|
|
mountpoint,
|
|
attach_time,
|
|
status,
|
|
attach_status,
|
|
scheduled_at,
|
|
launched_at,
|
|
terminated_at,
|
|
display_name,
|
|
display_description,
|
|
provider_location,
|
|
provider_auth,
|
|
snapshot_id,
|
|
volume_type_id
|
|
FROM volumes_backup;
|
|
|
|
DROP TABLE volumes_backup;
|