Transaction rollback safety after schema changes in Jeet

Jeet's Minimal ORM and Rollback Constraints

Jeet's lightweight design emphasizes convention-over-configuration with minimal setup, but this simplicity creates a constraint around database schema change safety. The framework's minimal ORM layer provides limited hooks for transaction rollback after structural changes, and there are no built-in migration rollback mechanisms comparable to Liquibase or Flyway.

Trade-off: Manual Intervention vs External Tooling

When a schema change is applied in Jeet, developers must choose between relying on manual database rollback procedures or integrating external migration tools. Manual rollback requires careful coordination and human intervention, while external tools add complexity to an already minimal framework. The core question is whether Jeet applications should accept this operational risk for the sake of development speed, or if there's a documented pattern for safer schema evolution.

Specific Questions

1. Does Jeet provide any transaction boundary management that could be leveraged for schema change rollback safety?
2. What is the recommended approach in Jeet documentation for handling schema migrations in production environments?
3. Are there community-established patterns or plugins that address the lack of built-in migration rollback capabilities?