Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add warning about lost custom operations #2713

Merged
merged 2 commits into from
Sep 29, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -200,4 +200,7 @@ It's also possible to reset all migrations and create a single one without losin
* Delete your **Migrations** folder
* Create a new migration and generate a SQL script for it
* In your database, delete all rows from the migrations history table
* Insert a single row into the migrations history, to record that the first migration has already been applied, since your tables are already there. The insert SEQL is the last operation in the SQL script generated above.
* Insert a single row into the migrations history, to record that the first migration has already been applied, since your tables are already there. The insert SQL is the last operation in the SQL script generated above.

> [!WARNING]
> Any [custom migration code](#customize-migration-code) will be lost when the **Migrations** folder is deleted. Any customizations must be applied to the new initial migration manually in order to be preserved.