Success
Something unexpected happened, you can open a GitHub issue or contact us.
Cannot find the schema review policy in a specific environment. Please follow the doc to create the policy.
Applications usually specifies database in their connection string. Dropping the database will definitely break those applications.
Renaming the table will break the code referring that table.
Dropping the table will break the code referring that table.
Renaming the column will break the code referring that column.
Dropping the column will break the code referring that column.
Primary key requires the candidate key set has unique value and the chosen candidate key set might not meet this requirement.
Unique key requires the candidate key set has unique value and the chosen candidate key set might not meet this requirement.
The existing values on the candidate foreign key and the referenced key might not meet the referential requirements.
The existing value might not meet the check requirement.
The existing value might not meet the check requirement.
Some ALTER COLUMN change is backward incompatible such as changing the data type from VARCHAR to INT. On the other hand, some change is backward compatible such as changing the database type from INT to BIGINT, or adding a comment and etc. User should review the actual statement.
A syntax error in your SQL statement.
The SQL has no WHERE clause. Check Require WHERE clause for details.
The SQL has SELECT *
. Check Disallow SELECT * for details.
The SQL has leading wildcard LIKE. Check Disallow leading % in LIKE for details.
The SQL has COMMIT
. Check Disallow COMMIT for details.
The SQL has redundant ALTER TABLE
. Check Merge ALTER TABLE for details.
The SQL dry-run failed. Check Dry run DML statements for details.
The SQL affected rows exceed the limit. Check Limit affected rows for details.
The SQL adds column with default value. Check Disallow add column with default for details.
The SQL adds check with validation. Check Add CHECK constraints with NOT VALID option for details.
The SQL adds NOT NULL. Check Disallow add NOT NULL constraints to an existing column for details.
Mismatch the table naming convention in your schema review policy. Check Table naming convention for details.
Mismatch the column naming convention in your schema review policy. Check Column naming convention for details.
Mismatch the index naming convention in your schema review policy. Check Index naming convention for details.
Mismatch the unique key naming convention in your schema review policy. Check Unique key naming convention for details.
Mismatch the foreign key naming convention in your schema review policy. Check Foreign key naming convention for details.
Mismatch the primary key naming convention in your schema review policy. Check Primary key naming convention for details.
Mismatch the auto-increment column naming convention in your schema review policy. Check Auto-increment column naming convention for details.
Cannot find the required columns defined in your schema review policy. Check Enforce the required columns in each table for details.
The column cannot be NULL
. Check Columns no NULL value for details.
The column type is changed. Check Disallow change column type for details.
The NOT NULL column has no default value. Check Set DEFAULT value for NOT NULL columns for details.
The column does not exist. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The column is changed with CHANGE COLUMN
. Check Disallow ALTER TABLE CHANGE COLUMN statements for details.
The column order is changed. Check Disallow changing column order for details.
The auto-increment column is not an integer. Check Use integer for auto-increment columns for details.
The column type is disabled. Check Column type disallow list for details.
The column already exists. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The column is dropped. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
Set the column charset. Check Disallow set charset for columns for details.
The char length exceeds the limit. Check Maximum CHAR length for details.
The auto-increment column initial value does not match. Check Auto-increment initial value for details.
The auto-increment column is signed. Check Set unsigned attribute on auto-increment columns for details.
The default current time column count exceeds the limit. Check Limit the count of current time columns for details.
The on update current time column count exceeds the limit. Check Limit the count of current time columns for details.
The column has no default value. Check Require column default value for details.
The column is referenced by view. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
Should se InnoDB as MySQL storage engine. Check Require InnoDB for details.
The table needs a primary key. Check Require primary key for details.
The table disallows the foreign key. Check Disallow foreign key for details.
The table name mismatches with the naming convention for drop table operation. Check Drop table naming convention for details.
The table does not exist. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The table already exists. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
Create table partition. Check Disallow partition table for details.
The table is referenced by views. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
Can only drop the database if there’s no table in it. Check Drop database restriction for details.
The database in your SQL statement mismatches with the database in the catalog. Please check the statement to ensure the database name is correct.
The database is deleted. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The query does not use any index.
The index key number exceeds the limit. Check Limit the count of index keys for details.
The index primary key type is not allowed. Check Limit key type for primary keys for details.
The index type is not allowed. Check Disallow BLOB and TEXT for index keys for details.
The index already exists. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The primary key already exists. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The index has no keys. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The primary key does not exist. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The index does not exist. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The index name is incorrect. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The spatial index key is nullable. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The index has duplicate columns. Check Disallow duplicate column in index keys for details.
The index count exceeds the limit. Check Index count limit for details.
The index is created without CONCURRENTLY. Check Create index concurrently for details.
The charset is disabled. Check Charset allow list for details.
The number of rows to be inserted exceeds the limit. Check Limit the inserted rows for details.
The UPDATE statement uses LIMIT. Check Disallow LIMIT for details.
The INSERT statement uses LIMIT. Check Disallow LIMIT for details.
The UPDATE statement uses ORDER BY. Check Disallow ORDER BY for details.
The DELETE statement uses ORDER BY. Check Disallow ORDER BY for details.
The DELETE statement uses LIMIT. Check Disallow LIMIT for details.
The INSERT statement does not specify columns. Check INSERT statements must specify columns for details.
The INSERT statement uses ORDER BY RAND. Check Disallow ORDER BY RAND in INSERT statements for details.
The collation is disabled. Check Collation allow list for details.
The comment is too long. Check Comment length limit for details.
The comment is empty. Check Comment convention for details.
The comment missing classification. Check Comment classification for details.
See Supported backup operations.
Success
Something unexpected happened, you can open a GitHub issue or contact us.
Cannot find the schema review policy in a specific environment. Please follow the doc to create the policy.
Applications usually specifies database in their connection string. Dropping the database will definitely break those applications.
Renaming the table will break the code referring that table.
Dropping the table will break the code referring that table.
Renaming the column will break the code referring that column.
Dropping the column will break the code referring that column.
Primary key requires the candidate key set has unique value and the chosen candidate key set might not meet this requirement.
Unique key requires the candidate key set has unique value and the chosen candidate key set might not meet this requirement.
The existing values on the candidate foreign key and the referenced key might not meet the referential requirements.
The existing value might not meet the check requirement.
The existing value might not meet the check requirement.
Some ALTER COLUMN change is backward incompatible such as changing the data type from VARCHAR to INT. On the other hand, some change is backward compatible such as changing the database type from INT to BIGINT, or adding a comment and etc. User should review the actual statement.
A syntax error in your SQL statement.
The SQL has no WHERE clause. Check Require WHERE clause for details.
The SQL has SELECT *
. Check Disallow SELECT * for details.
The SQL has leading wildcard LIKE. Check Disallow leading % in LIKE for details.
The SQL has COMMIT
. Check Disallow COMMIT for details.
The SQL has redundant ALTER TABLE
. Check Merge ALTER TABLE for details.
The SQL dry-run failed. Check Dry run DML statements for details.
The SQL affected rows exceed the limit. Check Limit affected rows for details.
The SQL adds column with default value. Check Disallow add column with default for details.
The SQL adds check with validation. Check Add CHECK constraints with NOT VALID option for details.
The SQL adds NOT NULL. Check Disallow add NOT NULL constraints to an existing column for details.
Mismatch the table naming convention in your schema review policy. Check Table naming convention for details.
Mismatch the column naming convention in your schema review policy. Check Column naming convention for details.
Mismatch the index naming convention in your schema review policy. Check Index naming convention for details.
Mismatch the unique key naming convention in your schema review policy. Check Unique key naming convention for details.
Mismatch the foreign key naming convention in your schema review policy. Check Foreign key naming convention for details.
Mismatch the primary key naming convention in your schema review policy. Check Primary key naming convention for details.
Mismatch the auto-increment column naming convention in your schema review policy. Check Auto-increment column naming convention for details.
Cannot find the required columns defined in your schema review policy. Check Enforce the required columns in each table for details.
The column cannot be NULL
. Check Columns no NULL value for details.
The column type is changed. Check Disallow change column type for details.
The NOT NULL column has no default value. Check Set DEFAULT value for NOT NULL columns for details.
The column does not exist. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The column is changed with CHANGE COLUMN
. Check Disallow ALTER TABLE CHANGE COLUMN statements for details.
The column order is changed. Check Disallow changing column order for details.
The auto-increment column is not an integer. Check Use integer for auto-increment columns for details.
The column type is disabled. Check Column type disallow list for details.
The column already exists. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The column is dropped. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
Set the column charset. Check Disallow set charset for columns for details.
The char length exceeds the limit. Check Maximum CHAR length for details.
The auto-increment column initial value does not match. Check Auto-increment initial value for details.
The auto-increment column is signed. Check Set unsigned attribute on auto-increment columns for details.
The default current time column count exceeds the limit. Check Limit the count of current time columns for details.
The on update current time column count exceeds the limit. Check Limit the count of current time columns for details.
The column has no default value. Check Require column default value for details.
The column is referenced by view. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
Should se InnoDB as MySQL storage engine. Check Require InnoDB for details.
The table needs a primary key. Check Require primary key for details.
The table disallows the foreign key. Check Disallow foreign key for details.
The table name mismatches with the naming convention for drop table operation. Check Drop table naming convention for details.
The table does not exist. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The table already exists. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
Create table partition. Check Disallow partition table for details.
The table is referenced by views. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
Can only drop the database if there’s no table in it. Check Drop database restriction for details.
The database in your SQL statement mismatches with the database in the catalog. Please check the statement to ensure the database name is correct.
The database is deleted. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The query does not use any index.
The index key number exceeds the limit. Check Limit the count of index keys for details.
The index primary key type is not allowed. Check Limit key type for primary keys for details.
The index type is not allowed. Check Disallow BLOB and TEXT for index keys for details.
The index already exists. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The primary key already exists. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The index has no keys. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The primary key does not exist. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The index does not exist. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The index name is incorrect. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The spatial index key is nullable. Found in Bytebase’s pre-execution checks, please confirm if there is a problem with the SQL.
The index has duplicate columns. Check Disallow duplicate column in index keys for details.
The index count exceeds the limit. Check Index count limit for details.
The index is created without CONCURRENTLY. Check Create index concurrently for details.
The charset is disabled. Check Charset allow list for details.
The number of rows to be inserted exceeds the limit. Check Limit the inserted rows for details.
The UPDATE statement uses LIMIT. Check Disallow LIMIT for details.
The INSERT statement uses LIMIT. Check Disallow LIMIT for details.
The UPDATE statement uses ORDER BY. Check Disallow ORDER BY for details.
The DELETE statement uses ORDER BY. Check Disallow ORDER BY for details.
The DELETE statement uses LIMIT. Check Disallow LIMIT for details.
The INSERT statement does not specify columns. Check INSERT statements must specify columns for details.
The INSERT statement uses ORDER BY RAND. Check Disallow ORDER BY RAND in INSERT statements for details.
The collation is disabled. Check Collation allow list for details.
The comment is too long. Check Comment length limit for details.
The comment is empty. Check Comment convention for details.
The comment missing classification. Check Comment classification for details.
See Supported backup operations.