From 88ff3c2fb3a006a4e8c467c8f75c5c9fe491f25e Mon Sep 17 00:00:00 2001 From: Daniel Iancu Date: Wed, 24 Feb 2016 09:18:33 +0200 Subject: [PATCH 1/3] Correct password column length in Authentication -> Database Considerations --- authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/authentication.md b/authentication.md index 73689d1f30c..95d6edda442 100644 --- a/authentication.md +++ b/authentication.md @@ -41,7 +41,7 @@ Don't worry if this all sounds confusing now! Most applications will never need By default, Laravel includes an `App\User` [Eloquent model](/docs/{{version}}/eloquent) in your `app` directory. This model may be used with the default Eloquent authentication driver. If your application is not using Eloquent, you may use the `database` authentication driver which uses the Laravel query builder. -When building the database schema for the `App\User` model, make sure the password column is 60 characters in length. +When building the database schema for the `App\User` model, make sure the password column is at least 60 characters in length, the default of 255 would be a good choice. Also, you should verify that your `users` (or equivalent) table contains a nullable, string `remember_token` column of 100 characters. This column will be used to store a token for "remember me" sessions being maintained by your application. This can be done by using `$table->rememberToken();` in a migration. From cecbd4b9dbff5710f652ff45fa9b71037a2be442 Mon Sep 17 00:00:00 2001 From: Eric Tendian Date: Wed, 24 Feb 2016 18:44:16 -0600 Subject: [PATCH 2/3] Noting issue with modifying columns where an enum is present in the table --- migrations.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/migrations.md b/migrations.md index dad386537fe..ba5350c6721 100644 --- a/migrations.md +++ b/migrations.md @@ -256,6 +256,8 @@ We could also modify a column to be nullable: $table->string('name', 50)->nullable()->change(); }); +> **Note:** Modifying any column in a table with an `enum` column is not currently supported. + #### Renaming Columns @@ -265,7 +267,7 @@ To rename a column, you may use the `renameColumn` method on the Schema builder. $table->renameColumn('from', 'to'); }); -> **Note:** Renaming columns in a table with a `enum` column is not currently supported. +> **Note:** Renaming any column in a table with an `enum` column is not currently supported. ### Dropping Columns From 41a03286a174d53e2ca3f13d2a194be245d45032 Mon Sep 17 00:00:00 2001 From: Eric Tendian Date: Wed, 24 Feb 2016 19:22:26 -0600 Subject: [PATCH 3/3] More clarifications to modification, renaming with an enum column --- migrations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/migrations.md b/migrations.md index ba5350c6721..f555b917f69 100644 --- a/migrations.md +++ b/migrations.md @@ -256,7 +256,7 @@ We could also modify a column to be nullable: $table->string('name', 50)->nullable()->change(); }); -> **Note:** Modifying any column in a table with an `enum` column is not currently supported. +> **Note:** Modifying any column in a table that also has a column of type `enum` is not currently supported. #### Renaming Columns @@ -267,7 +267,7 @@ To rename a column, you may use the `renameColumn` method on the Schema builder. $table->renameColumn('from', 'to'); }); -> **Note:** Renaming any column in a table with an `enum` column is not currently supported. +> **Note:** Renaming any column in a table that also has a column of type `enum` is not currently supported. ### Dropping Columns