Skip to main content

​
🚀 New Feature

Schema Review for SQL Editor sql-editor-schema-review
  • After setting up the schema review policy, if the SQL statement violates the error rule, Bytebase prevents SQL execution and shows error messages
    • Users can change the rule level from “Error” to “Warning”
      • If the SQL statement violates the updated schema review policy, Bytebase will run the SQL, but the warning message will display “Warning”
      • If schema review passes, Bytebase will run the SQL normally

​
🎄 Enhancements

  • Improved SQL Editor styles sql-editor-improvement
  • Improved SQL Editor experience with auto-completion and code formatting on the issue page
  • Support to set SSL connection arguments for ClickHouse instances
  • Support to Approve/Run all tasks in a stage for tenant mode deployment issues
  • Allow users to retry the schema migration task if it fails
  • Will not enforce migration version when users transfer a database to a tenant mode project

​
🎠 Community

  • Thanks to @Cluas for:
    • fix: pg ExecuteContext do not return err #1540
    • fix: remove early check since we support create database idempotent #1543
  • Thanks to @chiyutianyi for: feat: prometheus integration and pprof registration simplification #1550

​
⚙️ Install and Upgrade

Before upgrading: 1) Back up the metadata — in-place downgrade is not supported. 2) Do not run multiple containers on the same data directory. 3) Terraform users: upgrade Bytebase server first, then apply the new Terraform config.