doctrine / orm

lib/Doctrine/ORM/Tools/Console/Command/SchemaTool/CreateCommand.php

Indentation +4 added lines, -4 removed lines

@@ -43,9 +43,9 @@ 
     protected function configure()
     {
         $this->setName('orm:schema-tool:create')
-             ->setDescription('Processes the schema and either create it directly on EntityManager Storage Connection or generate the SQL output')
-             ->addOption('dump-sql', null, InputOption::VALUE_NONE, 'Instead of trying to apply generated SQLs into EntityManager Storage Connection, output them.')
-             ->setHelp(<<<EOT
+                ->setDescription('Processes the schema and either create it directly on EntityManager Storage Connection or generate the SQL output')
+                ->addOption('dump-sql', null, InputOption::VALUE_NONE, 'Instead of trying to apply generated SQLs into EntityManager Storage Connection, output them.')
+                ->setHelp(<<<EOT
 Processes the schema and either create it directly on EntityManager Storage Connection or generate the SQL output.
 
 <comment>Hint:</comment> If you have a database with tables that should not be managed
@@ -54,7 +54,7 @@ 
 
     \$config->setFilterSchemaAssetsExpression(\$regexp);
 EOT
-             );
+                );
     }
 
     /**

lib/Doctrine/ORM/Tools/Console/Command/SchemaTool/DropCommand.php

Indentation +6 added lines, -6 removed lines

@@ -43,11 +43,11 @@ 
     protected function configure()
     {
         $this->setName('orm:schema-tool:drop')
-             ->setDescription('Drop the complete database schema of EntityManager Storage Connection or generate the corresponding SQL output')
-             ->addOption('dump-sql', null, InputOption::VALUE_NONE, 'Instead of trying to apply generated SQLs into EntityManager Storage Connection, output them.')
-             ->addOption('force', 'f', InputOption::VALUE_NONE, "Don't ask for the deletion of the database, but force the operation to run.")
-             ->addOption('full-database', null, InputOption::VALUE_NONE, 'Instead of using the Class Metadata to detect the database table schema, drop ALL assets that the database contains.')
-             ->setHelp(<<<EOT
+                ->setDescription('Drop the complete database schema of EntityManager Storage Connection or generate the corresponding SQL output')
+                ->addOption('dump-sql', null, InputOption::VALUE_NONE, 'Instead of trying to apply generated SQLs into EntityManager Storage Connection, output them.')
+                ->addOption('force', 'f', InputOption::VALUE_NONE, "Don't ask for the deletion of the database, but force the operation to run.")
+                ->addOption('full-database', null, InputOption::VALUE_NONE, 'Instead of using the Class Metadata to detect the database table schema, drop ALL assets that the database contains.')
+                ->setHelp(<<<EOT
 Processes the schema and either drop the database schema of EntityManager Storage Connection or generate the SQL output.
 Beware that the complete database is dropped by this command, even tables that are not relevant to your metadata model.
 
@@ -57,7 +57,7 @@ 
 
     \$config->setFilterSchemaAssetsExpression(\$regexp);
 EOT
-             );
+                );
     }
 
     /**

lib/Doctrine/ORM/Tools/Console/Command/SchemaTool/UpdateCommand.php

Indentation +6 added lines, -6 removed lines

@@ -50,11 +50,11 @@ 
     protected function configure()
     {
         $this->setName($this->name)
-             ->setDescription('Executes (or dumps) the SQL needed to update the database schema to match the current mapping metadata')
-             ->addOption('complete', null, InputOption::VALUE_NONE, 'If defined, all assets of the database which are not relevant to the current metadata will be dropped.')
-             ->addOption('dump-sql', null, InputOption::VALUE_NONE, 'Dumps the generated SQL statements to the screen (does not execute them).')
-             ->addOption('force', 'f', InputOption::VALUE_NONE, 'Causes the generated SQL statements to be physically executed against your database.')
-             ->setHelp(<<<EOT
+                ->setDescription('Executes (or dumps) the SQL needed to update the database schema to match the current mapping metadata')
+                ->addOption('complete', null, InputOption::VALUE_NONE, 'If defined, all assets of the database which are not relevant to the current metadata will be dropped.')
+                ->addOption('dump-sql', null, InputOption::VALUE_NONE, 'Dumps the generated SQL statements to the screen (does not execute them).')
+                ->addOption('force', 'f', InputOption::VALUE_NONE, 'Causes the generated SQL statements to be physically executed against your database.')
+                ->setHelp(<<<EOT
 The <info>%command.name%</info> command generates the SQL needed to
 synchronize the database schema with the current mapping metadata of the
 default entity manager.
@@ -84,7 +84,7 @@ 
 
     \$config->setFilterSchemaAssetsExpression(\$regexp);
 EOT
-             );
+                );
     }
 
     /**

lib/Doctrine/ORM/Tools/Console/Command/ValidateSchemaCommand.php

Indentation +4 added lines, -4 removed lines

@@ -45,10 +45,10 @@
     protected function configure()
     {
         $this->setName('orm:validate-schema')
-             ->setDescription('Validate the mapping files')
-             ->addOption('skip-mapping', null, InputOption::VALUE_NONE, 'Skip the mapping validation check')
-             ->addOption('skip-sync', null, InputOption::VALUE_NONE, 'Skip checking if the mapping is in sync with the database')
-             ->setHelp('Validate that the mapping files are correct and in sync with the database.');
+                ->setDescription('Validate the mapping files')
+                ->addOption('skip-mapping', null, InputOption::VALUE_NONE, 'Skip the mapping validation check')
+                ->addOption('skip-sync', null, InputOption::VALUE_NONE, 'Skip checking if the mapping is in sync with the database')
+                ->setHelp('Validate that the mapping files are correct and in sync with the database.');
     }
 
     /**

lib/Doctrine/ORM/Tools/Console/Command/ClearCache/ResultCommand.php

Indentation +4 added lines, -4 removed lines

@@ -45,9 +45,9 @@ 
     protected function configure()
     {
         $this->setName('orm:clear-cache:result')
-             ->setDescription('Clear all result cache of the various cache drivers')
-             ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, cache entries will be flushed instead of deleted/invalidated.')
-             ->setHelp(<<<EOT
+                ->setDescription('Clear all result cache of the various cache drivers')
+                ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, cache entries will be flushed instead of deleted/invalidated.')
+                ->setHelp(<<<EOT
 The <info>%command.name%</info> command is meant to clear the result cache of associated Entity Manager.
 It is possible to invalidate all cache entries at once - called delete -, or flushes the cache provider
 instance completely.
@@ -64,7 +64,7 @@ 
 Finally, be aware that if <info>--flush</info> option is passed, not all cache providers are able to flush entries,
 because of a limitation of its execution nature.
 EOT
-             );
+                );
     }
 
     /**

lib/Doctrine/ORM/Tools/Console/Command/ClearCache/MetadataCommand.php

Indentation +4 added lines, -4 removed lines

@@ -45,9 +45,9 @@ 
     protected function configure()
     {
         $this->setName('orm:clear-cache:metadata')
-             ->setDescription('Clear all metadata cache of the various cache drivers')
-             ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, cache entries will be flushed instead of deleted/invalidated.')
-             ->setHelp(<<<EOT
+                ->setDescription('Clear all metadata cache of the various cache drivers')
+                ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, cache entries will be flushed instead of deleted/invalidated.')
+                ->setHelp(<<<EOT
 The <info>%command.name%</info> command is meant to clear the metadata cache of associated Entity Manager.
 It is possible to invalidate all cache entries at once - called delete -, or flushes the cache provider
 instance completely.
@@ -64,7 +64,7 @@ 
 Finally, be aware that if <info>--flush</info> option is passed, not all cache providers are able to flush entries,
 because of a limitation of its execution nature.
 EOT
-             );
+                );
     }
 
     /**

lib/Doctrine/ORM/Tools/Console/Command/ClearCache/QueryCommand.php

Indentation +4 added lines, -4 removed lines

@@ -45,9 +45,9 @@ 
     protected function configure()
     {
         $this->setName('orm:clear-cache:query')
-             ->setDescription('Clear all query cache of the various cache drivers')
-             ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, cache entries will be flushed instead of deleted/invalidated.')
-             ->setHelp(<<<EOT
+                ->setDescription('Clear all query cache of the various cache drivers')
+                ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, cache entries will be flushed instead of deleted/invalidated.')
+                ->setHelp(<<<EOT
 The <info>%command.name%</info> command is meant to clear the query cache of associated Entity Manager.
 It is possible to invalidate all cache entries at once - called delete -, or flushes the cache provider
 instance completely.
@@ -64,7 +64,7 @@ 
 Finally, be aware that if <info>--flush</info> option is passed, not all cache providers are able to flush entries,
 because of a limitation of its execution nature.
 EOT
-             );
+                );
     }
 
     /**

lib/Doctrine/ORM/Tools/Console/Command/ClearCache/QueryRegionCommand.php

Indentation +6 added lines, -6 removed lines

@@ -42,11 +42,11 @@ 
     protected function configure()
     {
         $this->setName('orm:clear-cache:region:query')
-             ->setDescription('Clear a second-level cache query region')
-             ->addArgument('region-name', InputArgument::OPTIONAL, 'The query region to clear.')
-             ->addOption('all', null, InputOption::VALUE_NONE, 'If defined, all query regions will be deleted/invalidated.')
-             ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, all cache entries will be flushed.')
-             ->setHelp(<<<EOT
+                ->setDescription('Clear a second-level cache query region')
+                ->addArgument('region-name', InputArgument::OPTIONAL, 'The query region to clear.')
+                ->addOption('all', null, InputOption::VALUE_NONE, 'If defined, all query regions will be deleted/invalidated.')
+                ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, all cache entries will be flushed.')
+                ->setHelp(<<<EOT
 The <info>%command.name%</info> command is meant to clear a second-level cache query region for an associated Entity Manager.
 It is possible to delete/invalidate all query region, a specific query region or flushes the cache provider.
 
@@ -70,7 +70,7 @@ 
 Finally, be aware that if <info>--flush</info> option is passed,
 not all cache providers are able to flush entries, because of a limitation of its execution nature.
 EOT
-             );
+                );
     }
 
     /**

lib/Doctrine/ORM/Tools/Console/Command/ClearCache/CollectionRegionCommand.php

Indentation +8 added lines, -8 removed lines

@@ -42,13 +42,13 @@ 
     protected function configure()
     {
         $this->setName('orm:clear-cache:region:collection')
-             ->setDescription('Clear a second-level cache collection region')
-             ->addArgument('owner-class', InputArgument::OPTIONAL, 'The owner entity name.')
-             ->addArgument('association', InputArgument::OPTIONAL, 'The association collection name.')
-             ->addArgument('owner-id', InputArgument::OPTIONAL, 'The owner identifier.')
-             ->addOption('all', null, InputOption::VALUE_NONE, 'If defined, all entity regions will be deleted/invalidated.')
-             ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, all cache entries will be flushed.')
-             ->setHelp(<<<EOT
+                ->setDescription('Clear a second-level cache collection region')
+                ->addArgument('owner-class', InputArgument::OPTIONAL, 'The owner entity name.')
+                ->addArgument('association', InputArgument::OPTIONAL, 'The association collection name.')
+                ->addArgument('owner-id', InputArgument::OPTIONAL, 'The owner identifier.')
+                ->addOption('all', null, InputOption::VALUE_NONE, 'If defined, all entity regions will be deleted/invalidated.')
+                ->addOption('flush', null, InputOption::VALUE_NONE, 'If defined, all cache entries will be flushed.')
+                ->setHelp(<<<EOT
 The <info>%command.name%</info> command is meant to clear a second-level cache collection regions for an associated Entity Manager.
 It is possible to delete/invalidate all collection region, a specific collection region or flushes the cache provider.
 
@@ -72,7 +72,7 @@ 
 Finally, be aware that if <info>--flush</info> option is passed,
 not all cache providers are able to flush entries, because of a limitation of its execution nature.
 EOT
-             );
+                );
     }
 
     /**

Spacing +1 added lines, -1 removed lines

@@ -97,7 +97,7 @@
         }
 
         if ($input->getOption('flush')) {
-            $collectionRegion  = $cache->getCollectionCacheRegion($ownerClass, $assoc);
+            $collectionRegion = $cache->getCollectionCacheRegion($ownerClass, $assoc);
 
             if ( ! $collectionRegion instanceof DefaultRegion) {
                 throw new \InvalidArgumentException(sprintf(