🐞 Bytebase error codes

Documentation for all error codes emitted by Bytebase.

General

Success

Something unexpected happened, you can open a GitHub issue or contact us.

Database

Please double check your username and password. Also check your firewall setting to make sure your database is network accessible to Bytebase.

A syntax error in your SQL statement.

Encountered an error when executing the SQL statement. If the error doesn't provide enough context, please open a GitHub issue or contact us.

Migration

Bytebase can't find the migration schema in the instance. When user successfully adds an instance to Bytebase, Bytebase will try to create a database called "bytebase" in the target instance. This database is the migration schema Bytebase relies on to store the migration history. Without this schema, any schema migration attempt will fail to proceed.

Bytebase observed that the same migration version has already applied to the target database. It could be multiple users creating the new migration changes around the same period and they pick the same version number.

Bytebase observed that a higher migration version has already applied to the target database. This normally suggests user doesn't follow sequential order to apply migration changes or there maybe multiple users creating migration changes around the same period.

For version control (VCS) based migration, we require the database to establish a basline first. See help doc for more details.

Backward Incompatible Migration

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.