In a large scale project, you may have to share your database with other parts of the project. There may be completely different teams working on different sections of your site, and those teams may not even be working in PHP. For example, let's say that you're company is so big it has a team dedicated to tracking the analytics, metrics, and performance against various KPI's that are important to the continued success of your company / product.
Well, it just so happens that if you leave Doctrine Migrations to its own devices, that it will quite happily delete anything it finds in your database that it doesn't have a matching Entity for. That's not so good, Al.
So, in this video we look at how to get around this problem. Hopefully this will save you from ever - accidentally - dropping required tables when running your migrations.
If you have found this video helpful, please consider sharing. I really appreciate it.
|1||Starting from scratch||16:52|
|2||Migrations for an Existing Project||05:04|
|3||Migrations for tables that are not Symfony / Doctrine entities||03:26|