From 23aa67e9abe440027aa07091beb35834e584e42e Mon Sep 17 00:00:00 2001 From: Shreyansh shrey Date: Sun, 3 Oct 2021 17:19:59 +0530 Subject: [PATCH] Typo: Changes name to username (#13504) Co-authored-by: Sascha Depold --- docs/manual/core-concepts/validations-and-constraints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/core-concepts/validations-and-constraints.md b/docs/manual/core-concepts/validations-and-constraints.md index cdc4139c9640..0ce8668f6a8f 100644 --- a/docs/manual/core-concepts/validations-and-constraints.md +++ b/docs/manual/core-concepts/validations-and-constraints.md @@ -46,7 +46,7 @@ Our code example above defines a unique constraint on the `username` field: } /* ... */ ``` -When this model is synchronized (by calling `sequelize.sync` for example), the `username` field will be created in the table as `` `name` TEXT UNIQUE``, and an attempt to insert an username that already exists there will throw a `SequelizeUniqueConstraintError`. +When this model is synchronized (by calling `sequelize.sync` for example), the `username` field will be created in the table as `` `username` TEXT UNIQUE``, and an attempt to insert an username that already exists there will throw a `SequelizeUniqueConstraintError`. ## Allowing/disallowing null values