Don't distinguish between truncate and drop during schema upgrades #41
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Research
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
slendium/ocd#41
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently the
UpgradeOptionsobject allows distinguishing between data loss through truncation and data loss through dropping columns, however there is no reason for these to be two separate properties.The intended use of these properties is to allow schema upgrades in two steps. One step before the data is destroyed where data in columns about-to-be-deleted/truncated can be transferred into new columns/tables and a second step where the old columns are truncated or removed.
Therefor, the
UpgradeOptionsobject can be simplified to have a single property called$allowLoss. Both$allowTruncateand$allowDropshould then be removed.The issue raised in #40 is still valid. Implementations should still prevent truncation, but any other modifications should still go through.
Combine allowTruncate and allowDrop into a single allowLoss propertyto Don't distinguish truncate and drop during schema upgradesDon't distinguish truncate and drop during schema upgradesto Don't distinguish between truncate and drop during schema upgrades