Function TestSanitizeQuery

backend/plugin/db/util/statement_parser_test.go:353–494

(t *testing.T)

}

func TestSanitizeQuery(t *testing.T) {
	tests := []struct {
		input   string
		want    []string
		wantErr bool
	}{
		{
			input: `
			--- 123456
			SELECT 1;
			--- 6312
			SELECT 2;
			---123
			---123
			/* 213123 */
			SELECT 3;
			`,
			want: []string{
				"SELECT 1", "SELECT 2", "SELECT 3",
			},
		},
		{
			input: `
-- This is the bytebase schema to track migration info for Spanner
-- Create a database called bytebase in the driver.
-- CREATE DATABASE bytebase;

-- Create migration_history table
CREATE TABLE migration_history (
    -- id is UUIDv4.
    id STRING(MAX) NOT NULL,
    created_by STRING(MAX) NOT NULL,
    created_ts INT64 NOT NULL,
    updated_by STRING(MAX) NOT NULL,
    updated_ts INT64 NOT NULL,
    -- Record the client version creating this migration history. For Bytebase, we use its binary release version. Different Bytebase release might
    -- record different history info and this field helps to handle such situation properly. Moreover, it helps debugging.
    release_version STRING(MAX) NOT NULL,
    -- Allows granular tracking of migration history (e.g If an application manages schemas for a multi-tenant service and each tenant has its own schema, that application can use namespace to record the tenant name to track the per-tenant schema migration)
    -- Since bytebase also manages different application databases from an instance, it leverages this field to track each database migration history.
    namespace STRING(MAX) NOT NULL,
    -- Used to detect out of order migration together with 'namespace' and 'version' column.
    sequence INT64 NOT NULL,
    CONSTRAINT sequence_is_non_negative CHECK (sequence >= 0),
    -- Current allowed values are BASELINE, MIGRATE, MIGRATE_SDL, BRANCH, DATA.
    type STRING(MAX) NOT NULL,
    -- Current allowed values are PENDING, DONE, FAILED.
    -- We create a "PENDING" record before applying the DDL and update that record to "DONE" after applying the DDL.
    status STRING(MAX) NOT NULL,
    -- Record the migration version.
    version STRING(MAX) NOT NULL,
    description STRING(MAX) NOT NULL,
    -- Record the migration statement
    statement STRING(MAX) NOT NULL,
    -- Record the schema after migration
    schema STRING(MAX) NOT NULL,
    -- Record the schema before migration. Though we could also fetch it from the previous migration history, it would complicate fetching logic.
    -- Besides, by storing the schema_prev, we can perform consistency check to see if the migration history has any gaps.