Field Deletion and Database Schema Permanence

ProcessWire manages field definitions and their corresponding database columns through a relational schema. When a field is deleted via the admin interface, the system removes both the field definition and the associated data columns from the database tables to maintain synchronization.

Because these schema modifications are applied immediately upon saving, there is no native transactional rollback mechanism to restore a deleted field and its associated data without relying on external SQL backups.

Design Constraints

• Field deletions are destructive actions.
• Schema changes are applied immediately to the database.
• No built-in "Undo" functionality exists for structural field removals.

Does ProcessWire provide a documented method to flag a field for archival instead of immediate deletion to prevent permanent data loss? If not, what is the recommended architectural approach to ensure schema safety during iterative field development?