You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disabling foreign key checks, truncating all tables and re-enabling foreign key checks is lightning-fast vs. the crawl of dropping and recreating all tables each time. What would be the downsides implementing this way?
I also have an issue with the fact that schema is dropped an re-create because I use triggers to perform some tasks (mainly to create history for some table, stored inside an another table).
As trigger are not managed by doctrine, they are not re-created when schema is re-created.
Disabling foreign key checks, truncating all tables and re-enabling foreign key checks is lightning-fast vs. the crawl of dropping and recreating all tables each time. What would be the downsides implementing this way?
The text was updated successfully, but these errors were encountered: