-
Notifications
You must be signed in to change notification settings - Fork 163
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
The generated migration drops the entire database #354
Comments
I think there is a clue as to why this is happening. I don't use doctrine mapping to manage my data. So it must be messing up the migration generation. On the other hand, I think it should be fixed so that the migration generation only creates the bundle requirement without considering the rest of the db. |
You should add the tables that you aren't using Doctrine to manage the mapping/schema for to your migrations configuration so that the Migrations library ignores them (see https://symfony.com/bundles/DoctrineMigrationsBundle/current/index.html#manual-tables for more on that). Otherwise, any time you run the None of the |
I had the same problem and I changed the RefreshToken entity to the following which solved the problem:
Doctrine does not handle Attributes and Annotations used together in one project. |
Hello,
I have a question of curiosity. I installed your bundle on my symfony 6 project and during the installation, I was quite amazed by the migration step.
When I went to check the migration before running it, I discovered that it includes a complete deletion of all the tables of my project.
I don't understand why the bundle takes care of the rest of the database instead of just its needs. I think it's dangerous, someone who runs the installation without checking could have very bad surprises 😄
Below is the migration generated by the bundle installation.
The text was updated successfully, but these errors were encountered: