Using Bytebase to facilitate Database Collaboration Between Developer and DBA

Photo by Green Chameleon on Unsplash

Using Bytebase to facilitate Database Collaboration Between Developer and DBA

Intro to Bytebase's UI workflow

Adela's photo
Adela
·Apr 28, 2022·

2 min read

Table of contents

  • 2 Roles - Project Owner & Developer
  • Developer Creates the SQL issue
  • DBA Reviews the SQL issue

If you haven't set up Bytebase for your team, please refer to my previous article: How to start using Bytebase for team database collaboration

2 Roles - Project Owner & Developer

Now we have a project prepared in Bytebase, and we have

  • Adela as Project Owner (usually the DBA to review SQLs)
  • Ray and Lucy as Project Developer

Those are two roles for a project in Bytebase. https://www.bytebase.com/docs/concepts/roles-and-permissions#project-roles

image.png

Developer Creates the SQL issue

OK, Adela already set up the project; now it's Ray's turn to change the database schema. We switch the account to Ray.

image.png

As Ray is a developer for Project Employee, she can view the project.

image.png

image.png

We skip the following setting for now. This article is for UI workflow only; I'll show you GitOps workflow in another one.

image.png

Ray has made a new feature -- to give every employee a choice to have a nickname.

image.png

All the code is ready; now, it's time to change the schema. Click project name Employee to go to the specific project page. Click Alter Schema.

image.png

This dialog popups up; she should choose the second one to make the pipeline work. image.png

image.png

image.png

Ray is not familiar with SQL queries; she searches around the internet and finds this.

w3schools.com/sql/sql_alter.asp

image.png

She fills in the title, SQL, applies the SQL to Prod, and assigns this issue to Adela for Prod review (As we configure in the previous article, only Prod requires manual review).

image.png

The basic check is running automatically.

image.png

The SQL runs successfully against the Test environment, which doesn't require manual approval, and then waits for approval for the Prod environment.

image.png

image.png

DBA Reviews the SQL issue

Now let's switch back to Adela to review.

image.png

image.png

image.png

image.png

After Adela clicks Resolve Issue, the issue is Done. image.png

If Adela goes back to the home page, she can see the closed issue.

image.png

Or go into the project page, the overview tab.

image.png

The migration history. image.png

 
Share this