You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Bytebase**: Every change to the database should proceed through an issue. The issue will automatically bring you **SQL Review**, **Custom Approval Flow** and other related features.
93
+
-**Bytebase**: Admin can configure whether to allow direct change or enforce the review process. When the review process is enforced, every change to the database will proceed through an issue. The issue will automatically bring you **SQL Review**, **Custom Approval Flow** and other related features.
Every change will be recorded in the **Change History**. Bytebase will also detect the schema changes made by other tools and mark them as **Schema Drift**.
Every change will be recorded in the **Change History**. Bytebase will also detect the schema changes made by other tools and mark them as **Schema Drift**.
If you write a SQL script such `ALTER TABLE` in **SQL Editor**, you'll either create a new issue or switch to **Admin mode** (similar to SSH in the terminal).
If you write a SQL script such `ALTER TABLE` in **SQL Editor**, you'll either create a new issue or switch to **Admin mode** (similar to SSH in the terminal).
On the other hand, the more common way to change the schema is to use **Schema Editor**.
102
104
@@ -129,7 +131,7 @@ On the other hand, the more common way to change the schema is to use **Schema E
129
131
Furthermore, `Admins`/`DBAs` can define semantic types for masking algorithms, such as email, phone, credit card, etc. As a result, the data will be masked according to the semantic type configured.
@@ -146,6 +148,18 @@ On the other hand, the more common way to change the schema is to use **Schema E
146
148
-**Bytebase**: **Audit Log** is available for the **Enterprise plan**. It records all the activities within Bytebase which can be filtered or exported.
-**CloudBeaver**: Support [GraphQL](https://github.com/dbeaver/cloudbeaver/wiki/Server-API-explorer), while the doc is pretty light.
154
+
155
+
-**Bytebase**: Support gRPC and HTTP/REST. Bytebase provides extensive [docs](/docs/api/overview/), [code samples](https://github.com/bytebase/api-example), and [tutorials](/tutorial/).
156
+
157
+
### GitOps
158
+
159
+
-**CloudBeaver**: In theory, you can build GitOps solution via the GraphQL API, but there is no mature solutions.
160
+
161
+
-**Bytebase**: [GitOps best practice](https://github.com/bytebase/api-example/tree/main/data-security) to configure every aspect of database security.
162
+
149
163
## Summary
150
164
151
165
This article compares Bytebase and CloudBeaver across various aspects, highlighting their unique strengths. CloudBeaver supports a wider range of databases, whereas Bytebase offers enhanced collaborative features for database management, including access control and change review capabilities. After all, in any use case, feel free to pick the one you're most comfortable with.
0 commit comments