Saturday, May 25, 2024
HomeWeb application programmingSymfonySymfony / Propel: How to Left Join

Symfony / Propel: How to Left Join

A JOIN is a way to connect related database tables by the common values between them. A left join contains all of the rows from the primary table plus related members of the second database if they exist. Using joins can significantly reduce the number of database queries required to render a web page. This Tech-Recipe describes how to do a left join in Symfony using Propel.

It is common to have tables linked by foreign keys. Obtaining information from the linked table can be accomplished by a left join.

In the below example, I have a primary Patient table that is linked to a Doc table by foreign keys. Not only do I want to list the associated doctor with a patient, I also want to list the associated doctor’s pager number.

Here is an cropped example schema.yml of my database structure:

    name:         varchar(255)
    name:         varchar(255)
    pager:        varchar(255)

First I perform my left join in my actions class:

$c = new Criteria();
$c->addJoin(PatientPeer::DOC_ID, DocPeer::ID, Criteria::LEFT_JOIN);
$this->patients = PatientPeer::doSelect($c);

Finally, I output the data in my template:

   foreach ($patients as $patient):
     echo $patient->getDoc()->getPager(); 

While this template code would work without the join, this technique with the join is more efficient. Without the join, the getDoc() method of the Patient model would have to make an extra database query for each iteration of the loop. With the join, the data required to hydrate the Doc objects and the Patient data are all gathered with a single database query.

David Kirk
David Kirk
David Kirk is one of the original founders of tech-recipes and is currently serving as editor-in-chief. Not only has he been crafting tutorials for over ten years, but in his other life he also enjoys taking care of critically ill patients as an ICU physician.


Please enter your comment!
Please enter your name here

Most Popular


Recent Comments

error: Content is protected !!