Bytebase Changelog

🚀 New Features#

• Selectively sync databases from an instance.
• Show the definition of TABLE and VIEW for Redshift and ClickHouse.

🚀 New Features#

• Add tooltips for tables, columns, and PostgreSQL view comments in SQL Editor.
• Support IM and webhook integration for Lark.
• Display table and view definition for Redshift.

🚀 New Features#

• Customizable homepage with shortcut list.
• Query for all nodes in Redis Cluster.
• Support for second-precision expiration time when granting project roles.

🚀 New Features#

• Support PostgreSQL role selection in DDL/DML issues.
• Add PostgreSQL database tenant mode option in project setting.
• Display package metadata for ORACLE on database page and SQL Editor.
• Support setting colors for environments for better visual distinction.
• Allow workspace admin to disable data export functionality.
• Add new SQL Review Rules for MySQL:
  • Prohibit DDL on specific tables for MySQL.
  • Prohibit DML on specific tables for MySQL.

🚀 New Features#

• Add an environment policy to allow executing DDL/DML statements directly in SQL Editor.
• Support data masking for BigQuery.
• Support rollback to a specific version in the change history on the database page.
• Add data access control and masking page under each project.

Check out our official 3.0 announcement - Bytebase 3.0 - DevSecOps for Database

🚀 New Features#

• AI Assistant for SQL Editor: Convert natural language into SQL, explain SQL queries and identifies potential problems.
• Support 1-click rollback for SQL Server DML change.
• Support gh-ost online schema change for MariaDB.
• Add new SQL Review Rules:
  • Require MAX_EXECUTION_TIME for MySQL.
  • Require MAX_STATEMENT_TIME for MariaDB.
  • Require ALGORITHM and LOCK options for online DDL in MySQL/MariaDB.
  • Table comment checks for PostgreSQL/Oracle.
  • Column comment checks for PostgreSQL/Oracle.
• Separate SQL review rules to disallow mixing statements in DDL or DML tasks.

🚀 New Features#

• Support applying changelists to database groups.
• Add a SQL Review rule for MySQL: Enforce classification in table/column comment.

🚀 New Features#

• Support synchronizing users and groups from Entra ID (former Azure AD).
• Support CockroachDB.
• Support project-level backup settings with auto-enable and skip error options.
• Real-time syntax checking in the SQL Editor.
• Support configuring password restriction.

🚀 New Features#

• One-click rollback for PostgreSQL DML change.

🚀 New Features#

• Allow assigning roles to groups at the workspace level.
• Support disallowing sign-in with email and password, allowing only SSO.
• Add a PostgreSQL SQL review rule: Disallow setting volatile default values on columns.

🚀 New Features#

• SQL Editor displays more inline schema details including tables, views, functions and stored procedures.
• Support SQL reviews via PR comments for GitOps workflows.
• The OpenAI feature is in Community Plan (free), allowing natural language to SQL in the SQL Editor by configuring your own OpenAI key.
• Support selecting data sources between Admin and Readonly modes in the SQL Editor, configurable at the environment or project level.
• Support for Microsoft Entra as a built-in OAuth2 SSO provider.
• Support using database labels as filters for database group conditions in raw expression format.
• Support for table_name as a risk factor for DDL and DML operations.

🚀 New Features#

• Support monitoring blocking sessions during PostgreSQL task execution.
• Support auto-completion for Oracle.
• Support Kerberos authentication for Hive.
• Sync extended property MS_Description on Table/Column as comment for SQL Server.

🚀 New Features#

• Support configuring SQL review rules by database engine.
• Support connecting to Redis sentinel and native cluster.
• Add project settings:
  • Allow SQL editing after issue creation.
  • Automatically close issues after rollout completion.
• Support WeCom direct messages for issue activities.

🚀 New Features#

• Support Databricks.
• Support TLS/SSL connection for SQL Server.
• Support Lark direct notifications for issue activities.
• Support email domain restriction for user sign-up.

🚀 New Features#

• Support DynamoDB.
• Support standalone SQL review issue.
• Support Slack direct messages for issue activities.
• Support prior backup for PostgreSQL.
• Add SQL Review Rule for SQL Server: Disallow redundant indexes.

🚀 New Features#

• Support user groups.
• Support BigQuery.
• Support sync schema for SQL Server.
• Support MongoDB cluster and direct connection to a node within a cluster.
• Support displaying detailed issue task execution logs for SQL Server and Oracle.
• Add SQL Review Rules:
  • Prohibit cross-database queries in SQL Server.
  • Prohibit performing calculations or calling functions in the 'WHERE' clause for SQL Server.
  • Prohibit creating functions or procedures in SQL Server.

🚀 New Features#

• Support configuring labels for issues.
• Support displaying detailed issue task execution logs (affected rows or errors) for MySQL and PostgreSQL.
• Support configuring table or column classification on the database page. In earlier versions, this required using DDL and was only supported for MySQL and PostgreSQL.
• Add two SQL Review rules:
  • Fully qualified object name for PostgreSQL.
  • Limit DDL operations on tables with large data volumes for MySQL.

🚀 New Features#

• Support DML change pre-backup for Oracle and SQL Server.
• Support display for procedures and functions in SQL Editor.
• Support storing database passwords in AWS Secrets Manager and GCP Secret Manager.
• Support IAM-based connections to Google Cloud SQL for MySQL and PostgreSQL.
• Support editing table partitions in schema editor for MySQL and TiDB.

🔔 Brand New GitOps#

The new GitOps workflow is not compatible with the old version, if you need assistance migrating to the new version, please consult us.

• Use access tokens for authentication.
• Support multiple VCS connectors in a project.
• Support specifying a database group as the target in the VCS connector, automatically applying to all databases in a project by default.
• Deprecate database name templates and latest schema write-back.