Conversation
…only on request - renamedFrom / dropped Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposal
0060. An entity's table outlives the file version that created it, and once the application holds data, renaming a field and retiring one look alike from the file alone: a name disappears and, for a rename, another appears. Read naively, a rename adds an empty column beside the old one (every existing row loses the value under its new name), and a removal deletes a column of production data with no step anyone could review.The proposed shape (expand/contract):
renamedFrom: <old field name>- applying the file renames the stored column in place, so the values move with the new name. It acts only while the old column exists and the new one does not, so it is harmless to leave in the file after the rename ran.dropped: [names]- former field / to-one relation names whose columns applying the file removes, data included. The explicit contract step.dropped:name orrenamedFrom:source the entity still declares (compared by the column the name maps to), a fieldrenamedFromits own name, arenamedFromsource also underdropped:, two fieldsrenamedFromthe same name, an empty name in either key.The proposal carries the exact specification text (a new subsection under Entities & fields, after unique - a business key over more than one field), the rows for the fields and entity-attribute tables, and the two Appendix A: DSL index rows. Per CONTRIBUTING, this PR does not touch
versions/; the release folds it in.Reference implementation: eclipse-dirigible/dirigible#7674 (issue eclipse-dirigible/dirigible#7635).
🤖 Generated with Claude Code