Deta Space schema migration and rollback compatibility

Deta Space provides a platform for deploying and managing decentralized applications. When updating the underlying data structures or schema definitions for a deployed project, maintaining backward compatibility is essential to prevent application downtime during a version transition.

A specific challenge arises when a schema change is deployed but must be reverted due to a regression. If the new schema involves destructive changes or incompatible type modifications, the state of the data may no longer align with the previous version of the application code.

• What mechanisms exist within Deta Space to ensure data remains accessible after rolling back to a previous application version following a schema update?
• Are there specific configuration constraints required to make schema changes rollback-safe?