Databases
StackOverflow2013
Postsdbo
POShould I use 'Join's in models, or call other models
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POShould I use 'Join's in models, or call other models
    primarykey
    data
    text
    <p>I'm in the process of learning OOPHP, and I'm looking for some 'best practice' advice.</p> <p>With a relational db, there's obviously foreign keys in many tables. When I am creating Models for my site I am trying to determine if it is better to do JOIN queries in the model, or have one model call another?</p> <p>Calling other models seems to keep the code more modular. Either way seem to create dependencies, whether it be on another table or anther model.</p> <p>If I go with the 'call other models' approach I seem to run into another problem: infinite loops. Here's the example I'm running into. I have 2 tables, <code>person</code> and <code>school</code>. Each <code>person</code> has a favorite school, represented by a <code>schoolId</code>. Each <code>school</code> has a <code>principal</code>, that is a <code>personId</code>.</p> <p>The <code>person</code> object the row is mapped to accepts a <code>school</code> object in its constructor, but the <code>school</code> object the school row is mapped to accepts a <code>person</code> object in its constructor.</p> <p>From what I've found, something about lazy loading, seems to be the solution, but (I could be wrong) it seems if I do that I can't use PHP's type hinting.</p> <p>(I'm guessing many will suggest an ORM tool like Doctrine to me, and it's something I will definitely look into in the future. I am avoiding it now because of its supposed steep learning curve, and because I feel I understand those tools better later on if I try it myself once)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStereško
    1. USAndrew Brown
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POShould I use 'Join's in models, or call other models
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POShould I use 'Join's in models, or call other models
      1. UShek2mgl
      1. VTFavorite
    3. VO
      singulars
      1. POShould I use 'Join's in models, or call other models
      1. This table or related slice is empty.
      1. VTClose
    1. COhaving a lot of models instead of joins do create dependencies and i dont think thats what you want to do. Using joins is normal and i dont see any problem with it.
      singulars
      1. POShould I use 'Join's in models, or call other models
      1. USGGio
    2. CObut don't join create dependencies as well? if a table is edited that is used in a ton of joins, you'll have to edit all those join queries. with many models, you'd update 1 model, and the changes would propagate to everyone that called it.
      singulars
      1. POShould I use 'Join's in models, or call other models
      1. USAndrew Brown
 

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