Databases
StackOverflow2013
Postsdbo
POZF2 Configuration Injection Or NOT?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POZF2 Configuration Injection Or NOT?
    primarykey
    data
    text
    <p>I've googled a lot and read as much as I can on the subject but I cannot find a direct answer to my question anywhere including here. My ZF2 application consists of roughly 7 different modules. 5 of the modules will need access to the same database configuration. The application itself has a database with roughly 124 different tables. So the idea here is to find the proper solution to write the least amount of code considering the setup.</p> <p>What I'm trying to do is create a specific class to interface with the DB. Where the business logic is kept in the Module and note the controllers to keep everything more abstract and easier to maintain. By that I mean controller X should be able to create a new instance of for instance (Application\Model\DBInterface) and use the models functions to do inserts deletes updates joins selects and so forth. The reason I would like to do it this way is so that all modules installed can use the same interface without having to write endless DI statements everywhere. So what I will need is an example of how I can get the configuration for the DB (currently inside module.config.php + local.php(username / pw)) to be passed to the Application\Model\DBInterface dbConfig variable, and perhaps even an instance of the dbAdapter initialized from config if possible.</p> <p>Alternatively I could potentially grab the configuration from the Application\Model\DBInterface if such a way exists.</p> <p>If neither of the above is possible then I can always go back to the old way of doing things by reading an ini file for the db details and instantiating my db adapter that way.</p> <p>Please keep in mind that I won't be injecting anything in the controllers as the controllers just <em>use</em> $db = new \Application\Model\DBInterface() so injecting into the controllers doesn't make much sense at all.</p> <p>Is there a better way to do this / optimized / am I doing it completely wrong? Anyone able to share some details please. I've spent way too much time on this already and definitely need help.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USWill H
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POZF2 Configuration Injection Or NOT?
      1. USWill H
      1. VTFavorite
    1. COOnce DI is setup, I recommend injecting *every* service. (Not everything is a service, but the DB access surely is! Then again, I only use DI in a statically typed environment so I don't need to worry about using the icky "Service Locator Pattern".)
      singulars
      1. POZF2 Configuration Injection Or NOT?
      1. This table or related slice is empty.
    2. COHow do you setup the DI for this though that's the question? I've seen countless articles on injecting to controllers which also means that you have to add di to each controller handling the 124 different tables. Right now doesn't seem like a very scalable solution to use di unless I'm completely misunderstanding
      singulars
      1. POZF2 Configuration Injection Or NOT?
      1. USWill H
    3. COI don't know how DI in PHP works, but if done right, it should be *less* complicated than using `new`s over the place. Once it's used anywhere, the cost of adding to any specific service should be trivial. It might be worthwhile into looking for a generator if the CRUD is predictable.
      singulars
      1. POZF2 Configuration Injection Or NOT?
      1. This table or related slice is empty.
 

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