What's Changed
- Schema Review for SQL Editor
馃殌 Features
- Schema Review for SQL Editor: 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 schema review policy, the warning message will display "Warning"
- If schema review passes, Bytebase will run the SQL normally
馃巹 Enhancements
- Improved SQL Editor styles
- 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 ExecuteConetxt 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
New Contributors
Full Changelog
release/1.1.1...release/1.2.0