Database-as-Code
. Database migration scripts are stored in a git repository. To make schema changes, a developer would create a migration script and submit for review in the corresponding VCS such as GitLab. After the script is approved and merged into the configured branch, Bytebase will automatically kicks off the task to apply the new schema change.
Issue
adds the collaboration such as approval, comment, and notification to the database change process. An issue is often created via the UI workflow. On the other hand, an issue may not be created via the GitOps workflow since the GitOps workflow may only need the rollout without further human intervention.
release
is a deployable unit that encapsulates a set of SQL statements.
Revision
records the versioned changes applied to a database. You can get a database from version A to version B by replaying the revisions between A and B. When applying a release to a database, the changes with a version present in the revision are skipped so that the same changes are not applied twice.
Changelog
records all changes applied to a database, whether they are versioned or not, successfully applied or not. This includes change database issues created on Bytebase UI or rollout via Bytebase APIs, but NOT changes from Bytebase SQL Editor or other external database tools. Changelog offers you insights into the database schema evolution.
Edit Schema
(DDL), Bytebase will take the schema snapshot before and after the change.