There's a closed report here: https://github.com/propelorm/Propel2/issues/1031
Though I'm sure that please remove size is not a good solution, since not every person can find this thread and learn that some sizes are default and due to a specific behavior of the compare tool, migrations are produced.
To raise a degree of the issue, we faced a complete downtime of the system, when the migration:
ALTER TABLE product CHANGE custom_idcustom_id INTEGER;
since the table contains 100 M lines.
Other cases, causing permanent migration, please see table definition (all in one)
Please copy schema, generate diff and apply changes to the DB.
Then just generate diff again.
I'm getting:
DROP INDEX `index-brand_slug-slug` ON `brand_slug`;
ALTER TABLE `brand_slug`
CHANGE `created_at` `created_at` TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
CHANGE `price` `price` INTEGER(11) NOT NULL;
CREATE INDEX `index-brand_slug-slug` ON `brand_slug` (`slug`);
My ideas of the way how to fix this:
fail generation of the diff/schema - if the size is wrongly specified.
There's a closed report here: https://github.com/propelorm/Propel2/issues/1031 Though I'm sure that
please remove size
is not a good solution, since not every person can find this thread and learn that some sizes aredefault
and due to a specific behavior of the compare tool, migrations are produced.To raise a degree of the issue, we faced a complete downtime of the system, when the migration:
since the table contains 100 M lines.
Other cases, causing permanent migration, please see table definition (all in one)
Please copy schema, generate diff and apply changes to the DB. Then just generate diff again. I'm getting:
My ideas of the way how to fix this: