diff --git a/docs/data-types/mysql.md b/docs/data-types/mysql.md index d9c38ddc0d..8707807a52 100644 --- a/docs/data-types/mysql.md +++ b/docs/data-types/mysql.md @@ -146,7 +146,7 @@ It can be manually added to the DDL via an `ALTER TABLE` command. While Spanner supports check constraints, the Spanner migration tool currently migrates all valid check constraints from MySQL to Spanner. -During the prepare migration phase, if any invalid or unsupported check constraints are identified, the migration process will be halted and will not commence. This is to ensure the integrity and accuracy of the migration. Any identified issues will be clearly displayed in the Issues & Suggestions tab. This allows the user to review all errors in detail. The user will then have the opportunity to manually address these errors by either correcting the invalid check constraints or removing them altogether. This step is crucial to ensure that all constraints are compatible with the target system, thereby preventing potential issues during or after the migration process. Once the necessary corrections have been made, the user can proceed to re-initiate the migration process without any unsupported constraints. +While moving from schema to prepare migration phase, if any invalid or unsupported check constraints are identified, the migration process will be halted and will not commence. This is to ensure the integrity and accuracy of the migration. Any identified issues will be clearly displayed in the Issues & Suggestions tab. This allows the user to review all errors in detail. The user will then have the opportunity to manually address these errors by either correcting the invalid check constraints or removing them altogether. This step is crucial to ensure that all constraints are compatible with the target system, thereby preventing potential issues during or after the migration process. Once the necessary corrections have been made, the user can proceed to re-initiate the migration process without any unsupported constraints. > Note: As check constraints were introduced with MySQL version 8.0.16, the Spanner migration tool will automatically include these constraints in the Spanner draft for databases using this version or later. For MySQL versions prior to 8.0.16, where check constraints are not supported, users will need to manually incorporate any required check constraints into the Spanner draft. This approach ensures that all necessary constraints are accurately represented in the Spanner environment, tailored to the specific needs of the database. diff --git a/ui/dist/ui/index.html b/ui/dist/ui/index.html index b1bffb018a..e1012fc95a 100644 --- a/ui/dist/ui/index.html +++ b/ui/dist/ui/index.html @@ -7,10 +7,10 @@ - - + +