Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When using the command:
$ php app/console doctrine:schema:create
We get this message
ATTENTION: This operation should not be executed in a production environment.
Why shouldn’t we use it in production ?
How should we do the first deployment ?
Ahaha there are different schools for that.
Startup way: doctrine:schema:create first time in production, doctrine:schema:update –force every updates
Cautious way: dump sql first time, sql scripts then for updates
Expert way: http://symfony.com/doc/master/bundles/DoctrineMigrationsBundle/index.html
Personally I use the first method, which works just fine. You could always do a –dump-sql to see what’s going on before updating using –force