baseline scripts executed unexpectedly about bytebase

[tianzhou]

Converted from #350

[tianzhou]

@qsliu2017 please take a look.

To setup a ClickHouse instance, you can follow:

https://bytebase.com/blog/how-to-run-clickhouse-with-docker-and-connect-using-mysql-client

[qsliu2017]

I find that baseline SQL script will always be executed, both UI and Git workflow

In bytebase docs, it says

...This is achieved by using a baseline migration script which includes the entire schema of that live database.
...
Internally, the baseline migration only causes Bytebase to update its migration history table to record the baseline state. It won't apply the SQL statements in that baseline file to the corresponding database since the database is the origin source of the baseline and already has all the schema.

@tianzhou ,I need more info about

1. does the baseline script need statements?
2. should the baseline script be executed?

[tianzhou]

I find that baseline SQL script will always be executed, both UI and Git workflow

In bytebase docs, it says

...This is achieved by using a baseline migration script which includes the entire schema of that live database.
...
Internally, the baseline migration only causes Bytebase to update its migration history table to record the baseline state. It won't apply the SQL statements in that baseline file to the corresponding database since the database is the origin source of the baseline and already has all the schema.

@tianzhou ,I need more info about

1. does the baseline script need statements?
2. should the baseline script be executed?

What baseline means is it tells Bytebase the current state of schema (aka establishing the baseline)

So Baseline statement does has statement, it's the statement tells Bytebase the current schema.

But it should NOT be executed.