Bytebase 3.7.0
Support Batch Export
π New Features
- Support batch data export from multiple databases or a database group via issue.
- Support batch data export from limited databases in the SQL Editor.
- Support requesting any project roles.
- Support displaying
CHECK
constraints in the SQL Editor. - Trino - Support data masking.
- MariaDB - Support sql_type in risk condition.
- SQL Server - Support columnstore index.
π Notable Changes
π° Pricing
- Custom approval is no longer restricted by instance limits. It now only requires an Enterprise subscription. Previously, it was limited to licensed instances β now it applies to any instance under an Enterprise plan.
π¨ GUI
-
Remove Earliest allowed time. Use Scheduled time during rollout instead.
-
The gh-ost and backup toggles are now set at the issue level, no longer at the task level.
-
The SQL statement is now defined at the issue level, no longer at the task level. Once a task has started or completed, the statement cannot be updated.
π§© API
-
Remove
earliest_allowed_time
fromPlan.spec
. Userun_at
inBatchRunTasksRequest
instead. -
Remove
steps
andtarget
fromPlan
. Usespecs
andtargets
respectively. -
Remove
PreviewPlan
RPC fromPlanService
. -
Update
ChangeDatabaseConfig
:- Remove
BASELINE
fromType
. - Remove
schema_version
. - Add
release
.
- Remove
-
Update setting names, use the correct values as defined in SettingName.
π Enhancements
- PostgreSQL - Issue tickets now honor any supplied
SET search_path
, so subsequent SQL statements (and their DML rollback logic) operate on the specified schema rather than defaulting to public. - Trino - Enhance auto-completion support.
- TiDB - Improve syntax error detection.
- TiDB - The βrequire primary keyβ rule now checks the source table when using
CREATE TABLE LIKE
.
π Bug Fixes
- Doris and StarRocks - Resolve compatibility issues.
- RedShift - Fix connection database parameter issue.
βοΈ Install and Upgrade
-
Fresh install: /get-started/self-host
-
Upgrade: /get-started/upgrade
Warning 1): Bytebase does not support in-place downgrade. Make sure to back up your metadata before upgrading. 2) Never run multiple containers on the same data directory. Stop and remove the old one first to avoid corruption.