All geek questions in one place

Prevent Doctrine diff migration from deleting tables

I am currently doing "Doctrinizing" a large existing database. This process works very well, and we can slowly replace the old raw query code with entities and DQL.

We recently discovered the amazing Doctrine Migrations project, which seems like the perfect candidate for managing change in our database. However, we encountered some problem.

Our database is quite large, and we will reorganize aspects of our application in different ways. Currently, we have about 40% of the database represented as entities. The problem is that when we run diff in a partially transformed database, diff wants to dump many tables, because there are no entities for these tables. We can edit the diff manually, but it will become rather cumbersome and potentially error prone.

The question arises: is it possible to create diff and say that the diff process does not drop any tables for which there are no objects?

+4
source share
1 answer

Symfony2, , : http://symfony.com/doc/current/bundles/DoctrineMigrationsBundle/index.html#manual-tables

, diff, :

app/console doctrine:migrations:diff --filter-expression=/^t_/

( diff , t_ ).

+5

Source: https://habr.com/ru/post/1535663/

More articles:


All Articles