Re: Handling database creation and migration

[Andrus Adamchik]

I am checking my migrations archive, and "Cayenne-friendly" schema alterations 
or simple INSERT/UPDATE/DELETE make up probably 50% of those. The rest are 
things like these:

(1)

LOAD DATA LOCAL INFILE './patches-5.0/some.csv' INTO TABLE some_table 
 FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY '\n' 
(C1,C2,C3); 

(2)

SET unique_checks=0;

ALTER TABLE t1 DROP INDEX keyword_index;
ALTER TABLE t1 DROP INDEX headline_index;
ALTER TABLE t1 ENGINE=InnoDB;

SET unique_checks=1;

(3)

set @AAA = (select max(ID) from nhldb.xxx);
insert into nhldb.xxx (ID, NAME, DESCRIPTION, URL)
values((@AAA+1), 's1', 's2', 's3');

So how would those be handled if we are to go this route?

Andrus