AWS aurora-dsql documentation change
Summary
Added documentation for 'ADD table_constraint_using_index' syntax to add UNIQUE constraints using existing indexes
Security assessment
The change adds documentation for a new ALTER TABLE syntax feature for adding constraints using existing indexes. This is a database functionality enhancement with no security implications mentioned in the diff.
Diff
diff --git a/aurora-dsql/latest/userguide/alter-table-syntax-support.md b/aurora-dsql/latest/userguide/alter-table-syntax-support.md index a5282c970..03742353a 100644 --- a//aurora-dsql/latest/userguide/alter-table-syntax-support.md +++ b//aurora-dsql/latest/userguide/alter-table-syntax-support.md @@ -7 +7 @@ -Identity column actions +Identity column actionsAdd constraint actions @@ -27,0 +28 @@ Identity column actions + ADD table_constraint_using_index @@ -31,0 +33,5 @@ Identity column actions + and table_constraint_using_index is: + + [ CONSTRAINT constraint_name ] + UNIQUE USING INDEX index_name + @@ -45,0 +52,13 @@ This form removes the identity property from a column. If `DROP IDENTITY IF EXIS +## Add constraint actions + +**`ADD`table_constraint_using_index``** + + +This form adds a new `UNIQUE` constraint to a table based on an existing unique index. All the columns of the index will be included in the constraint. + +The index must be in a `VALID` state; adding a unique constraint using an index while the index is currently building is not supported. + +If a constraint name is provided then the index will be renamed to match the constraint name. Otherwise the constraint will be named the same as the index. + +After this command is executed, the index is "owned" by the constraint, in the same way as if the index had been built by a regular `CREATE UNIQUE INDEX ASYNC` command. In particular, dropping the constraint will make the index disappear too. +