Skip to content

Commit 61a5292

Browse files
Update README.md
1 parent 5ce01ad commit 61a5292

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

README.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Laravel's standard mechanism for [squashing migrations](https://laravel.com/docs
1414
is very good, but it has a huge drawback - it only exports the database schema and the contents of
1515
a single table - `migrations`.
1616

17-
And this approach is quite acceptable on small projects where you need to quickly reduce the number of migration files
17+
And this approach is quite acceptable on small projects where you need to quickly reduce the number of migration files,
1818
and there is no binding to the table contents.
1919

2020
But what if you have a large project with several people working on it, and you constantly run tests that must contain
@@ -26,8 +26,6 @@ unloads the data from your selected tables into SQL file.
2626

2727
All you need to do is install the package and add the new setting to the `config/database.php` file and that's it.
2828

29-
Let's get down to business!
30-
3129
## Requirements
3230

3331
- Laravel 10, 11
@@ -83,7 +81,8 @@ return [
8381

8482
After that, add to the array the names of the tables for which you want to export data.
8583

86-
That's it. Now run the `php artisan schema:dump` console command and enjoy the result.
84+
That's it. Now run the [`php artisan schema:dump`](https://laravel.com/docs/migrations#squashing-migrations)
85+
console command and enjoy the result.
8786

8887

8988
## License

0 commit comments

Comments
 (0)