Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Simple solution</strong></p> <p>If you're implementing a Symfony command (that can be executed in a cron tab), you can access the service container from the command.</p> <pre><code>&lt;?php namespace MyProject\MyBundle\Command; use Symfony\Bundle\FrameworkBundle\Command\ContainerAwareCommand; use Doctrine\ORM\EntityManager; use Symfony\Component\Console\Input\InputInterface; use Symfony\Component\Console\Output\OutputInterface; class UpdateCommand extends ContainerAwareCommand { protected $em; protected function configure() { $this-&gt;setName('myproject:mybundle:update') ; } protected function execute(InputInterface $input, OutputInterface $output) { $this-&gt;em = $this-&gt;getContainer()-&gt;get('doctrine.orm.entity_manager'); } } </code></pre> <p>That way, you get the entity manager from a command and don't need to declare this class as a service. You can therefore remove the configuration you added in the <code>services.yml</code> file.</p> <p><strong>An other solution (cleaner)</strong></p> <p>This solution allows better separation of concerns and can therefore be easily unit tested and reused in other parts of your Symfony application (not only as a command).</p> <p>Move all the logic part of your "update" command to a dedicated class that you will declare as a service:</p> <pre><code>&lt;?php namespace MyProject\MyBundle\Service; use Doctrine\ORM\EntityManager; class MyUpdater { protected $em; public function __construct($em) { $this-&gt;em = $em; } public function runUpdate() { // All your logic code here } } </code></pre> <p>Declare it as a service in your <code>services.yml</code> file:</p> <pre><code>services: myproject.mybundle.myupdater: class: MyProject\MyBundle\Service\MyUpdater arguments: ['@doctrine.orm.entity_manager'] </code></pre> <p>Simply call your service from your command :</p> <pre><code>&lt;?php namespace MyProject\MyBundle\Command; use Symfony\Bundle\FrameworkBundle\Command\ContainerAwareCommand; use Symfony\Component\Console\Input\InputInterface; use Symfony\Component\Console\Output\OutputInterface; class UpdateCommand extends ContainerAwareCommand { protected function configure() { $this-&gt;setName('myproject:mybundle:update') ; } protected function execute(InputInterface $input, OutputInterface $output) { $myUpdater = $this-&gt;getContainer()-&gt;get('myproject.mybundle.myupdater'); $myUpdater-&gt;runUpdate(); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POSymfony2 getdoctrine outside of Model/Controller
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMichaël Perrin
    1. USMichaël Perrin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSymfony2 getdoctrine outside of Model/Controller
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COyes, is exactly this what I want to do. but now im getting a different error: PHP Fatal error: Call to a member function getKernel() on a non-object in /var/www/project/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Command/ContainerAwareCommand.php on line 36. I.m following the cookbook and I dont understand this error
      singulars
      1. PO
      1. USBrunoRamalho
    2. COI edited my code and this error is fixed. You have to move the initialization to the `execute` method.
      singulars
      1. PO
      1. USMichaël Perrin
    3. CO`ContainerAwareCommand` is just a class that itself extends `ContainerAware` ... @BrunoRamalho you didnt mention you're trying to get the entity-manager inside a command but you were talking about general non-controller classes so this answer is only an addition to mine.
      singulars
      1. PO
      1. USnifr
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload