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
@@ -41,7 +44,7 @@ protected function configure(): void
41
44
->addOption('group', null, InputOption::VALUE_IS_ARRAY | InputOption::VALUE_REQUIRED, 'Only load fixtures that belong to this group (use with --services)')
42
45
->addOption('append', null, InputOption::VALUE_NONE, 'Append the data fixtures instead of flushing the database first.')
43
46
->addOption('dm', null, InputOption::VALUE_REQUIRED, 'The document manager to use for this command.')
44
-
->addOption('purge-with-delete', null, InputOption::VALUE_NONE, 'Use deleteMany() to purge the collections instead of dropping them. This is useful to keep the collections, their metadata and their indexes, but it is slower than dropping them.')
47
+
->addOption('purge', null, InputOption::VALUE_OPTIONAL, 'Purge the database before loading the fixtures. If set to "delete", collections will be kept and documents deleted instead of dropping the collections.', null, self::getPurgeModes(...))
45
48
->setHelp(<<<'EOT'
46
49
The <info>doctrine:mongodb:fixtures:load</info> command loads data fixtures from your application:
47
50
@@ -55,9 +58,9 @@ protected function configure(): void
If the collection uses search indexes or encryption, you can use the <info>--purge-with-delete</info> option to keep the collections instead of dropping them when purging the database:
61
+
If the collection uses search indexes or encryption, you can use the <info>--purge=delete</info> option to keep the collections instead of dropping them when purging the database:
0 commit comments