diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/CreateDatabaseDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/CreateDatabaseDoctrineCommand.php index b084d21fdb..777503ed97 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/CreateDatabaseDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/CreateDatabaseDoctrineCommand.php @@ -34,12 +34,12 @@ class CreateDatabaseDoctrineCommand extends DoctrineCommand The doctrine:database:create command creates the default connections database: -./app/console doctrine:database:create +php app/console doctrine:database:create You can also optionally specify the name of a connection to create the database for: -./app/console doctrine:database:create --connection=default +php app/console doctrine:database:create --connection=default EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/DropDatabaseDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/DropDatabaseDoctrineCommand.php index 173b249928..8f50fc40e1 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/DropDatabaseDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/DropDatabaseDoctrineCommand.php @@ -34,14 +34,14 @@ class DropDatabaseDoctrineCommand extends DoctrineCommand The doctrine:database:drop command drops the default connections database: -./app/console doctrine:database:drop +php app/console doctrine:database:drop The --force parameter has to be used to actually drop the database. You can also optionally specify the name of a connection to drop the database for: -./app/console doctrine:database:drop --connection=default +php app/console doctrine:database:drop --connection=default Be careful: All data in a given database will be lost when executing this command. diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/GenerateEntitiesDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/GenerateEntitiesDoctrineCommand.php index aab2c7ded6..65d568ae21 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/GenerateEntitiesDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/GenerateEntitiesDoctrineCommand.php @@ -43,27 +43,27 @@ You have to limit generation of entities: * To a bundle: - ./app/console doctrine:generate:entities MyCustomBundle + php app/console doctrine:generate:entities MyCustomBundle * To a single entity: - ./app/console doctrine:generate:entities MyCustomBundle:User - ./app/console doctrine:generate:entities MyCustomBundle/Entity/User + php app/console doctrine:generate:entities MyCustomBundle:User + php app/console doctrine:generate:entities MyCustomBundle/Entity/User * To a namespace - ./app/console doctrine:generate:entities MyCustomBundle/Entity + php app/console doctrine:generate:entities MyCustomBundle/Entity If the entities are not stored in a bundle, and if the classes do not exist, the command has no way to guess where they should be generated. In this case, you must provide the --path option: - ./app/console doctrine:generate:entities Blog/Entity --path=src/ + php app/console doctrine:generate:entities Blog/Entity --path=src/ You should provide the --no-backup option if you don't mind to back up files before to generate entities: - ./app/console doctrine:generate:entities Blog/Entity --no-backup + php app/console doctrine:generate:entities Blog/Entity --no-backup Important: Even if you specified Inheritance options in your XML or YAML Mapping files the generator cannot generate the base and diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/ImportMappingDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/ImportMappingDoctrineCommand.php index f8aa6cc48c..efbd8aa49f 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/ImportMappingDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/ImportMappingDoctrineCommand.php @@ -42,22 +42,22 @@ class ImportMappingDoctrineCommand extends DoctrineCommand The doctrine:mapping:import command imports mapping information from an existing database: -./app/console doctrine:mapping:import "MyCustomBundle" xml +php app/console doctrine:mapping:import "MyCustomBundle" xml You can also optionally specify which entity manager to import from with the --em option: -./app/console doctrine:mapping:import "MyCustomBundle" xml --em=default +php app/console doctrine:mapping:import "MyCustomBundle" xml --em=default If you don't want to map every entity that can be found in the database, use the --filter option. It will try to match the targeted mapped entity with the provided pattern string. -./app/console doctrine:mapping:import "MyCustomBundle" xml --filter=MyMatchedEntity +php app/console doctrine:mapping:import "MyCustomBundle" xml --filter=MyMatchedEntity Use the --force option, if you want to override existing mapping files: -./app/console doctrine:mapping:import "MyCustomBundle" xml --force +php app/console doctrine:mapping:import "MyCustomBundle" xml --force EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/InfoDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/InfoDoctrineCommand.php index 7d435c719b..acebd82e1b 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/InfoDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/InfoDoctrineCommand.php @@ -34,12 +34,12 @@ The doctrine:mapping:info shows basic information about which entities exist and possibly if their mapping information contains errors or not. -./app/console doctrine:mapping:info +php app/console doctrine:mapping:info If you are using multiple entity managers you can pick your choice with the --em option: -./app/console doctrine:mapping:info --em=default +php app/console doctrine:mapping:info --em=default EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearMetadataCacheDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearMetadataCacheDoctrineCommand.php index b7849fdc48..e8cff147d6 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearMetadataCacheDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearMetadataCacheDoctrineCommand.php @@ -36,12 +36,12 @@ class ClearMetadataCacheDoctrineCommand extends MetadataCommand The doctrine:cache:clear-metadata command clears all metadata cache for the default entity manager: -./app/console doctrine:cache:clear-metadata +php app/console doctrine:cache:clear-metadata You can also optionally specify the --em option to specify which entity manager to clear the cache for: -./app/console doctrine:cache:clear-metadata --em=default +php app/console doctrine:cache:clear-metadata --em=default EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearQueryCacheDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearQueryCacheDoctrineCommand.php index 649b6a67d0..1e509d3f12 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearQueryCacheDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearQueryCacheDoctrineCommand.php @@ -36,12 +36,12 @@ class ClearQueryCacheDoctrineCommand extends QueryCommand The doctrine:cache:clear-query command clears all query cache for the default entity manager: -./app/console doctrine:cache:clear-query +php app/console doctrine:cache:clear-query You can also optionally specify the --em option to specify which entity manager to clear the cache for: -./app/console doctrine:cache:clear-query --em=default +php app/console doctrine:cache:clear-query --em=default EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearResultCacheDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearResultCacheDoctrineCommand.php index 3624945b98..e6dcfeea4f 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearResultCacheDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ClearResultCacheDoctrineCommand.php @@ -36,27 +36,27 @@ class ClearResultCacheDoctrineCommand extends ResultCommand The doctrine:cache:clear-result command clears all result cache for the default entity manager: -./app/console doctrine:cache:clear-result +php app/console doctrine:cache:clear-result You can also optionally specify the --em option to specify which entity manager to clear the cache for: -./app/console doctrine:cache:clear-result --em=default +php app/console doctrine:cache:clear-result --em=default If you don't want to clear all result cache you can specify some additional options to control what cache is deleted: -./app/console doctrine:cache:clear-result --id=cache_key +php app/console doctrine:cache:clear-result --id=cache_key Or you can specify a --regex to delete cache entries that match it: -./app/console doctrine:cache:clear-result --regex="user_(.*)" +php app/console doctrine:cache:clear-result --regex="user_(.*)" You can also specify a --prefix or --suffix to delete cache entries for: -./app/console doctrine:cache:clear-result --prefix="user_" --suffix="_frontend" +php app/console doctrine:cache:clear-result --prefix="user_" --suffix="_frontend" EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ConvertMappingDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ConvertMappingDoctrineCommand.php index 67c4e82cb7..080527d2b3 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ConvertMappingDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/ConvertMappingDoctrineCommand.php @@ -39,7 +39,7 @@ class ConvertMappingDoctrineCommand extends ConvertMappingCommand The doctrine:mapping:convert command converts mapping information between supported formats: -./app/console doctrine:mapping:convert xml /path/to/output +php app/console doctrine:mapping:convert xml /path/to/output EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/CreateSchemaDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/CreateSchemaDoctrineCommand.php index 4e329e1d79..70413c559b 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/CreateSchemaDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/CreateSchemaDoctrineCommand.php @@ -39,15 +39,15 @@ class CreateSchemaDoctrineCommand extends CreateCommand The doctrine:schema:create command executes the SQL needed to generate the database schema for the default entity manager: -./app/console doctrine:schema:create +php app/console doctrine:schema:create You can also generate the database schema for a specific entity manager: -./app/console doctrine:schema:create --em=default +php app/console doctrine:schema:create --em=default Finally, instead of executing the SQL, you can output the SQL: -./app/console doctrine:schema:create --dump-sql +php app/console doctrine:schema:create --dump-sql EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/DropSchemaDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/DropSchemaDoctrineCommand.php index d2fc103024..60d92c05ce 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/DropSchemaDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/DropSchemaDoctrineCommand.php @@ -38,16 +38,16 @@ class DropSchemaDoctrineCommand extends DropCommand The doctrine:schema:drop command generates the SQL needed to drop the database schema of the default entity manager: -./app/console doctrine:schema:drop --dump-sql +php app/console doctrine:schema:drop --dump-sql Alternatively, you can execute the generated queries: -./app/console doctrine:schema:drop --force +php app/console doctrine:schema:drop --force You can also optionally specify the name of a entity manager to drop the schema for: -./app/console doctrine:schema:drop --em=default +php app/console doctrine:schema:drop --em=default EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/EnsureProductionSettingsDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/EnsureProductionSettingsDoctrineCommand.php index 8e61b00143..c8534a732e 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/EnsureProductionSettingsDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/EnsureProductionSettingsDoctrineCommand.php @@ -37,12 +37,12 @@ class EnsureProductionSettingsDoctrineCommand extends EnsureProductionSettingsCo The doctrine:ensure-production-settings command ensures that Doctrine is properly configured for a production environment.: -./app/console doctrine:ensure-production-settings +php app/console doctrine:ensure-production-settings You can also optionally specify the --em option to specify which entity manager to use: -./app/console doctrine:ensure-production-settings --em=default +php app/console doctrine:ensure-production-settings --em=default EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/RunDqlDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/RunDqlDoctrineCommand.php index b202edd5d5..e71ae788fe 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/RunDqlDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/RunDqlDoctrineCommand.php @@ -37,17 +37,17 @@ class RunDqlDoctrineCommand extends RunDqlCommand The doctrine:query:dql command executes the given DQL query and outputs the results: -./app/console doctrine:query:dql "SELECT u FROM UserBundle:User u" +php app/console doctrine:query:dql "SELECT u FROM UserBundle:User u" You can also optional specify some additional options like what type of hydration to use when executing the query: -./app/console doctrine:query:dql "SELECT u FROM UserBundle:User u" --hydrate=array +php app/console doctrine:query:dql "SELECT u FROM UserBundle:User u" --hydrate=array Additionally you can specify the first result and maximum amount of results to show: -./app/console doctrine:query:dql "SELECT u FROM UserBundle:User u" --first-result=0 --max-result=30 +php app/console doctrine:query:dql "SELECT u FROM UserBundle:User u" --first-result=0 --max-result=30 EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/RunSqlDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/RunSqlDoctrineCommand.php index 8fb16f99dd..c45faf5a84 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/RunSqlDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/RunSqlDoctrineCommand.php @@ -37,7 +37,7 @@ class RunSqlDoctrineCommand extends RunSqlCommand The doctrine:query:sql command executes the given DQL query and outputs the results: -./app/console doctrine:query:sql "SELECT * from user" +php app/console doctrine:query:sql "SELECT * from user" EOT ); } diff --git a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/UpdateSchemaDoctrineCommand.php b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/UpdateSchemaDoctrineCommand.php index cdb2a579e8..346fae8368 100644 --- a/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/UpdateSchemaDoctrineCommand.php +++ b/src/Symfony/Bundle/DoctrineBundle/Command/Proxy/UpdateSchemaDoctrineCommand.php @@ -43,15 +43,15 @@ default entity manager. For example, if you add metadata for a new column to an entity, this command would generate and output the SQL needed to add the new column to the database: -./app/console doctrine:schema:update --dump-sql +php app/console doctrine:schema:update --dump-sql Alternatively, you can execute the generated queries: -./app/console doctrine:schema:update --force +php app/console doctrine:schema:update --force You can also update the database schema for a specific entity manager: -./app/console doctrine:schema:update --em=default +php app/console doctrine:schema:update --em=default EOT ); }