Last week, we released Bytebase 1.8.0. Let's take a deeper look into some of the new features.
MySQL Sync Schema
You can now specify to synchronize the schema from database A to database B, and Bytebase will automatically generate the intermediate DDL statements to be executed.
Usually, developers make database changes in the test environment first and then apply the changes to the prod environment afterward. Before Sync Schema, you need to carefully write out the statements that need to be changed by themselves. Now, you can simply let Bytebase know which database schema needs to be applied to the target database.
We are planning to add Sync Schema support for PostgreSQL soon.
Admin Mode for SQL Editor
A key selling point of Bytebase is that all scenarios that need database access can be done through Bytebase (aside from the app itself accessing the database). Before this release, Bytebase could already perform database changes and queries on behalf of the application developers.
However, dedicated DBAs, or those responsible for database operations in DevOps teams, need to perform higher privileged operations.Admin Mode meets this need, and it is only available to DBAs or Owner role holders in a workspace and needs to be switched on manually in the SQL Editor.
Thus, all scenarios in which human beings deal with databases can be performed via Bytebase, except for those where the application deals with the database. Companies no longer need to distribute database access keys or configure separate bastion/jump servers, as Bytebase controls access and operations. Bytebase also identifies dangerous statements, reducing the chance of human mistakes, while the DBA can configure SQL review policy and control database access at the global level.
