Chapters

27 Chapters | 2:45:18 |

01

The Answer Entity

5:32
02

The ManyToOne Relation

8:35
03

Saving Relations

3:58
04

Relations in Foundry

4:41
05

Foundry: Always Pass a Factory Instance to a Relation

4:57
06

Fetching Relations

6:58
07

Rendering Answer Data & Saving Votes

6:02
08

Owning Vs Inverse Sides of a Relation

7:11
09

Relation OrderBy & fetch=EXTRA_LAZY

7:22
10

Filtering to Return only Approved Answers

9:40
11

Collection Criteria for Custom Relation Queries

6:33
12

Most Popular Answers Page

6:23
13

The |u Filter & String Component

4:11
14

Joining Across a Relationship & The N + 1 Problem

6:30
15

Search, the Request Object & OR Query Logic

8:05
16

The 4 (2?) Possible Relation Types

4:02
17

ManyToMany Relation

4:53
18

Saving Items in a ManyToMany Relation

6:36
19

Handling ManyToMany in Foundry

4:01
20

Joining Across a ManyToMany

5:22
21

ManyToMany... with Extra Fields on the Join Table?

6:57
22

When a Migration Falls Apart

6:23
23

QuestionTag Fixtures & DateTimeImmutable with Faker

4:07
24

Doing Crazy things with Foundry & Fixtures

8:59
25

JOINing Across Multiple Relationships

3:52
26

Pagination with Pagerfanta

6:20
27

Themed Pagination Links

7:07

This tutorial has a new version, check it out!

> Symfony 5 > Symfony 5: Mastering Doctrine Relations

Buy Access to Course

09.

Relation OrderBy & fetch=EXTRA_LAZY

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Challenge

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

10 Comments

Sort By

Login or Register to join the conversation

Szymon 3 years ago

Hey,
How to obtain the same effect with @ORM\OrderBy({"createdAt" = "DESC"}) in PHP8?
When I am using #[ORM\OrderBy(createdAt: 'DESC')] it causes an error - Unknown named parameter 'createdAt'

|

MolloKhan SFCASTS Szymon 3 years ago

Hey Szymon,

I'm afraid you forgot to import the TimestampableEntity trait in your class. Let me know if that helps

Cheers!

|

Szymon MolloKhan 3 years ago

Hello MolloKhan,
Of course I have it in my Question class. I think problem is with #[ORM\OrderBy(createdAt: 'DESC')] syntax.
I have tried a lot of combinations but can't figure out what is the case.

|

MolloKhan SFCASTS Szymon 3 years ago

Oh, I think this is the syntax you need #[ORM\OrderBy(['createdAt' => 'DESC'])]

1 |

Trendency 3 years ago edited

This Code write you
`class AppFixtures extends Fixture
{

public function load(ObjectManager $manager)
{
    AnswerFactory::new(function() use ($questions) {
        return [
            'question' => $questions[array_rand($questions)]
        ];
    })->needsApproval()->many(20)->create();
}

}`

But a few episodes ago u use this shortcut
class AppFixtures<br /> AnswerFactory::createMany(100);
this shortcutis good for this epidose I think
class AppFixtures<br /> AnswerFactory::createMany(100);<br /> AnswerFactory::new()->needsApproval()->many(20)->create();<br />
Cheers!

|

Sebastian-O 4 years ago

As I understood this chapter, TWIG triggers SQL-Queries, in other word, TWIG initiates additional DB-connections. Really? Until now I thought, only the controller (& services) triggers the SQL-queries via Doctrine and passes the results to TWIG via the return-array, so TWIG just could use what the controller already produced. Now which is correct?

|

Victor SFCASTS Sebastian-O 4 years ago

Hey Planschkuh1992,

Yes, that's right. With ORM thing a bit more complicated, because you can query from the DB for example a user object, then pass it to the template, where you will call "user.getOrders()" and iterate over user's orders to list them. Doctrine may not load those orders initially for performance reason when you fetch the object from the DB, because probably you will never need that data. But on the explicit request of those data that happened in the template, additional queries might be sent to the DB to fetch that extra information. And it's kinda OK, because first of all, that's handled by third-party logic of that ORM, it's not about you sending a DB query directly from the template, right? it's happening behind the scene. But if you got access to the DB connection in the template and wrote a query that will hit the DB from inside the template - it would be a bad practice for sure.

That's just one example. I hope it clarify things for you.

Cheers!

1 |

davidmintz 4 years ago

are we just going to live with the N+1 problem? ....oops sorry my bad. I see we will get to that in Chapter 14.

|

weaverryan SFCASTS davidmintz 4 years ago

Haha, no problem. And yes, often I DO just live with the N+1 problem anyways... Blackfire is great for showing me when that's *actually* a problem :).

Cheers!

|

davidmintz weaverryan 4 years ago

often I DO just live with the N+1 problem

What?? I am a bit too obsessive-compulsive for that :-) seriously though --- I have created an ambitious Doctrine project and it works brilliantly, but there were a few spots where I never did figure out how to cut the queries down to as few as I believed they should be, and a lot of hoop-jumping to fix N+1. Part of my motivation for being here is to learn Doctrine better -- iow to get more inDoctrinated.

|

Symfony 5.3 Doctrine 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.2",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "babdev/pagerfanta-bundle": "^3.3", // v3.3.0
        "composer/package-versions-deprecated": "^1.11", // 1.11.99.3
        "doctrine/doctrine-bundle": "^2.1", // 2.4.2
        "doctrine/doctrine-migrations-bundle": "^3.0", // 3.1.1
        "doctrine/orm": "^2.7", // 2.9.5
        "knplabs/knp-markdown-bundle": "^1.8", // 1.9.0
        "knplabs/knp-time-bundle": "^1.11", // v1.16.1
        "pagerfanta/doctrine-orm-adapter": "^3.3", // v3.3.0
        "pagerfanta/twig": "^3.3", // v3.3.0
        "sensio/framework-extra-bundle": "^6.0", // v6.2.1
        "stof/doctrine-extensions-bundle": "^1.4", // v1.6.0
        "symfony/asset": "5.3.*", // v5.3.4
        "symfony/console": "5.3.*", // v5.3.7
        "symfony/dotenv": "5.3.*", // v5.3.7
        "symfony/flex": "^1.3.1", // v1.21.6
        "symfony/framework-bundle": "5.3.*", // v5.3.7
        "symfony/monolog-bundle": "^3.0", // v3.7.0
        "symfony/runtime": "5.3.*", // v5.3.4
        "symfony/stopwatch": "5.3.*", // v5.3.4
        "symfony/twig-bundle": "5.3.*", // v5.3.4
        "symfony/validator": "5.3.*", // v5.3.14
        "symfony/webpack-encore-bundle": "^1.7", // v1.12.0
        "symfony/yaml": "5.3.*", // v5.3.6
        "twig/extra-bundle": "^2.12|^3.0", // v3.3.1
        "twig/string-extra": "^3.3", // v3.3.1
        "twig/twig": "^2.12|^3.0" // v3.3.2
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.3", // 3.4.0
        "symfony/debug-bundle": "5.3.*", // v5.3.4
        "symfony/maker-bundle": "^1.15", // v1.33.0
        "symfony/var-dumper": "5.3.*", // v5.3.7
        "symfony/web-profiler-bundle": "5.3.*", // v5.3.5
        "zenstruck/foundry": "^1.1" // v1.13.1
    }
}

Previous Challenge

Next Chapter