Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You shouldn't use <code>static</code> here at all. Just create a container: <code>$container = new DIContainer();</code> and use that object as a typical dependency. After all there's a very few places in the core of application that require access to the whole container.</p> <p>Take a look at <a href="https://github.com/symfony/DependencyInjection">Symfony's Dependency Injection component</a> - piece of quite good code.</p> <hr> <h3>EDIT:</h3> <p>According to the first comment. Yes, you've misunderstood me. Usually you'd need only several dependencies from the container, so you'll write something like:</p> <pre><code>$service = new Service($container-&gt;get('dep.a'), $container-&gt;get('dep.b'), 123); </code></pre> <p>My point was that you shouldn't use static property within the container, as it makes it nothing more but a global object. There would be no difference between:</p> <pre><code>global $container; $widget = new Widget($container-&gt;fetch('widgetDep')); $kumquat = new Kumquat($container-&gt;fetch('kumquatDep')); $widget = new Widget(Container::getInstance()-&gt;fetch('widgetDep')); $kumquat = new Kumquat(Container::getInstance()-&gt;fetch('kumquatDep')); // You're using new objects but they share the same, **global** array. // Therefore, they are actually global themselves. $widget = new Widget((new Container())-&gt;fetch('widgetDep')); $kumquat = new Kumquat((new Container())-&gt;fetch('kumquatDep')); </code></pre> <p>In other words, the Container itself should be a local variable, and if you'll need to access it somewhere else (some objects might need access to the entire container) then you should explicitly pass it as dependency to that object.</p> <p>As I said before, take a look at Symfony DIC and the whole framework to see how to make a good, well-written DIC.</p> <hr> <p>Simple container:</p> <pre><code>class Container { private $services = array(); public function get($service) { if (!array_key_exists($this-&gt;services, $service)) { throw ...; } return $this-&gt;services[$service]; } } $containerA = new Container(); $containerB = new Container(); // $containerA and $containerB are completely different // objects and don't share anything </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODoes PHP 5.4 object dereferencing successfully mitigate the drawbacks of static storage parameter in this DI container?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCrozin
    1. USCrozin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODoes PHP 5.4 object dereferencing successfully mitigate the drawbacks of static storage parameter in this DI container?
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COPerhaps I've misunderstood, but wouldn't that approach suffer from the fault I mentioned about passing an entire container of dependencies to an object when it only needs a single dependency from inside the container? It seems like passing an entire container as a dependency is itself only the lesser of two evils. It's better than a full-blown service locator, but still not ideal. And an object doesn't have a dependency on a container, it has a dependency on an object inside the container. It seems that approach masks your real dependencies? As Miško Hevery says, "Ask, don't look," right?
      singulars
      1. PO
      1. USrdlowrey
    2. CO@rdlowrey: I've updated my answer.
      singulars
      1. PO
      1. USCrozin
    3. COAha, now I see your point. I thought you were suggesting just passing along the entire container as a dependency itself. Your update makes sense.
      singulars
      1. PO
      1. USrdlowrey
 

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