Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What you know from Zend Framework 1.x is an "Application Resource".</p> <p>The concept of "application resource" is replaced in Zend Framework 2 by so-called <a href="http://en.wikipedia.org/wiki/Domain-driven_design#Building_blocks_of_DDD" rel="nofollow">"services"</a> (intro <a href="http://blog.evan.pro/introduction-to-the-zend-framework-2-servicemanager" rel="nofollow">here</a>)</p> <p>An other change is modules themselves. In ZF1, a module was mainly a sub-section of your application that handled some requests. This is no longer true in ZF2: if your module defines a service or controller, that one is now accessible to all the application. There's a nice intro on some <a href="http://blog.hock.in/zf2-for-zf1-users-part-1" rel="nofollow">differences between ZF1 and ZF2 by Gary Hockin</a>.</p> <p>But anyway, modules are <em>NOT</em> self-contained. They should be developed in insulated environment and with as little dependencies as possible, but they provide cross-concerns functionality that affects all of your application.</p> <p>For your specific case of the logger, I suggest that your module always defines a logger and consumes it. What can be done to define the logger conditionally is following:</p> <pre><code>class MyModule { public function onBootstrap($e) { // $e-&gt;getTarget() is the \Zend\Mvc\Application $sm = $e-&gt;getTarget()-&gt;getServiceManager(); if (!$sm-&gt;has('some-logger-name')) { $sm-&gt;setFactory('some-logger-name', function ($sl) { return new MyLogger($sl-&gt;get('some-db')); }); } } } </code></pre> <p>You would then be able to use your 'some-logger-name' across all your application.</p> <p>A different approach is to just define the logger services and let other modules or configurations override it later on:</p> <pre><code>class MyModule { public function getConfig() { return array( 'service_manager' =&gt; array( 'factories' =&gt; array( 'some-logger-name' =&gt; 'My\Logger\Factory\ClassName' ), ), ); } } </code></pre> <p>Same is achieved with <code>getServiceConfig</code>, which is less flexible and cannot be cached, but has higher priority over <code>getConfig</code> (allows overrides) and lets you also define service factories as closures:</p> <pre><code>class MyModule { public function getServiceConfig() { return array( 'factories' =&gt; array( 'some-logger-name' =&gt; function ($sl) { return new MyLogger($sl-&gt;get('some-db')); }, ), ); } } </code></pre> <p>You could then even define a config key that has to be used to decide which logger (service name) to use.</p> <p>The concept with modules and configurations is that "last module wins", so you may define the service <code>'some-logger-name'</code> either in your module or in any module loaded before it.</p> <p>Same concepts apply also to your DB connection.</p> <p>As you can see, moving to services already gave you a certain degree of freedom. </p> <p>Keep in mind that it is not that the "Application" defines something for you: modules define your services/configs/events etc... The running application is then a composition of all these things together.</p>
    singulars
    1. This table or related slice is empty.
    1. POZend Framework 2 - Applications / Modules / Service Managers - Oh My
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USOcramius
    1. USOcramius
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POZend Framework 2 - Applications / Modules / Service Managers - Oh My
      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. COI greatly appreciate the writeup (and quickly glanced through the link you provided, I will go through it in depth a little later today). Due to the struggle I was having (partially noted in the question post above), I have also started to read through ZF2 source code to get a better understanding of the workflow. Your response is very well explained coupled with reading the source code, I am starting to get a much better grasp on how the pieces fit together. I am looking forward to the read (link) you provided as at a quick glance it looks like exactly what I need to move from ZF1 to ZF2!
      singulars
      1. PO
      1. USAaron Murray
    2. COGiven how new the release of ZF2, along with the amount of change in process to a service managed / event driven style, there is huge amount of obscurity in the information available so far (at least from what I have come across), I very much appreciate the link you provided as it seems to describe the transition well.
      singulars
      1. PO
      1. USAaron Murray
    3. CO@AaronMurray master `ServiceManager` and `EventManager` and everything will look much much easier.
      singulars
      1. PO
      1. USOcramius
 

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