-
Notifications
You must be signed in to change notification settings - Fork 662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
baseline scripts executed unexpectedly #394
Comments
Converted from #350 |
@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 |
I find that baseline SQL script will always be executed, both UI and Git workflow In bytebase docs, it says
@tianzhou ,I need more info about
|
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. |
Discussed in #350
Originally posted by NickStepanov January 10, 2022
Hi,
I am trying to test the use of Clickhouse with VCS based workflow.
I am creating a UI based baseline and it works fine.
After that, I am pushing a file to gitlab with my baseline, it get picked up by Bytebase and it even states:
SQL (This is a baseline migration and bytebase won't apply the SQL to the database, it will only record a baseline history)
After that, in the created issue, I try to click
run
, thinking that it will not touch my db, but I getexecute query ..... Table ...... already exists
It looks like my baseline file is trying to be executed my live db.
Is that an issue? Or am I doing something wrong?
Nik
The text was updated successfully, but these errors were encountered: