Environment-Specific Database Schema Modifications

When making changes to the database schema, such as adding, removing, or renaming columns, it's crucial to ensure that these modifications do not unintentionally affect the production environment. I propose adding a feature that allows developers to perform schema changes exclusively within designated development environments. This capability would ensure that any alterations made during development remain isolated and do not propagate to production, thereby protecting the live application from potential disruptions. Implementing this feature would enhance the safety and flexibility of managing database schemas, enabling smoother development workflows while maintaining the stability and integrity of the production system.