ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Context Weblate relies on Django's migration framework for schema changes, splitting operations into schema and data migrations. While schema migrations are generally reversible, data migrations using RunPython or RunSQL require explicit reverse_code to support rollback. The official upgrade documentation recommends database backups before upgrades and state
Goal Ensure that Cypher queries reflect the latest schema state without manual intervention. Constraints & Uncertainty Neo4j’s plan cache stores compiled execution plans to avoid re‑planning. The cache is not automatically invalidated when indexes, constraints, or labels are added or removed. Consequently, a query that previously used an index may contin
Rails migrations expose a DSL intended for reversible schema evolution, yet the boundary between the framework's automatic rollback inference and the underlying relational database's DDL semantics remains an unresolved design concern. Teams need a predictable contract for when db:rollback can safely invert a schema change without manual intervention. The cor
Goal Ensure that rolling back a schema migration does not inadvertently lose or corrupt data. Current Constraints Ecto requires a down function for every migration; if omitted the migration is deemed irreversible. The alter table DSL does not automatically generate reverse operations for added columns or renamed fields, and the :force option can silently tru
Background Grunt‑migrate’s grunt migrate:down reverts the last migration file, but only the schema alterations are guaranteed to be undone. When a migration performs data transformations without an explicit down section, the plugin documentation states that no automatic data rollback occurs. This can leave orphaned rows or inconsistent state after a rollback
weblate
neo4j
rails
ecto
grunt