We’ve ran into a few fights with the delayed column dropping mechanism lately. These are rare issues but they cause a lot of pain, relatively speaking. The question is : is there any way to manually force the columndropper to run? Details of the issues in case anyone is interested: run migration…

You could trick the system into believing that the first migration ran more than one hour ago. spec/components/migration/column_dropper_spec.rb dd810b8b0 UPDATE schema_migration_details SET created_at = :created_at WHERE id = (SELECT MIN(id) …

Maybe @tgxworld or @sam could comment, as they have time.

Our plan is to introduce a new system that is not subject to these issues in the next few weeks, we will announce it on meta when ready

[imagen] Introducing Post Deployment Migration dev As of https://github.com/discourse/discourse/commit/40fa96777ddad4698df20d6b8a61afcf87743ed7 , we’re moving away from our delayed drop pattern to remove a column from a table in the database. Inspired by Gitlab’s pattern of…

Problemas retrasados de columndropper

Soporte

david (David Taylor) 14 Junio, 2021 08:48 6

Tema		Respuestas	Vistas
Introducing Post Deployment Migration Development	0	1628	8 Octubre 2018
Failure to pay attention to SKIP POST DEPLOYMENT MIGRATIONS causes problems Support	7	1010	1 Abril 2022
Discourse Upgrade from 3.2.0 to 3.3.0 Postgress issue Self-hosting	2	152	24 Octubre 2024
New installation fails on migration Bug	5	1164	14 Abril 2020
Recovering from failed/partially applied upgrade Self-hosting	49	2681	12 Agosto 2022

Problemas retrasados de columndropper

Temas relacionados