Chapters

16 Chapters | 1:26:33 |

01

Doctrine DQL

7:38
02

The QueryBuilder

2:02
03

andWhere() and orWhere()

7:06
04

JOINs

3:45
05

JOINs and addSelect Reduce Queries

5:22
06

EXTRA_LAZY Relationships

6:07
07

SELECT the SUM (or COUNT)

6:15
08

Selecting Specific Fields

5:09
09

SELECTing into a New DTO Object

3:40
10

Raw SQL Queries

6:52
11

Reusing Queries in the Query Builder

4:42
12

Criteria: Filter Relation Collections

9:09
13

Filters: Automatically Modify Queries

6:59
14

WHERE IN()

2:07
15

Using RAND() or Other Non-Supported Functions

3:11
16

Using GROUP BY to Fetch & Count in 1 Query

6:29

> Symfony > Go Pro with Doctrine Queries

Buy Access to Course

09.

SELECTing into a New DTO Object

|

|

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 $6.00

Previous Challenge

Next Challenge

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

18 Comments

Sort By

Login or Register to join the conversation

ameotoko 1 year ago

Actually, in this specific case I would still probably prefer selecting to an array, because then I could just spread it in the controller:

return $this->render('fortune/showCategory.html.twig',[
    'category' => $category,
    ...$result
]);

But it's still a cool lesson, good to know this feature exists!

1 |

Victor SFCASTS ameotoko 1 year ago

Hey Andrey,

Thanks for sharing this tip! Yeah, the new PHP syntax gives you more flexibility and in some cases might be pretty useful. DTO is also cool because it gives you an object and autocompletion in some cases, just choose wherever fits your needs better.

Cheers!

|

julien_bonnier 3 years ago

Woah!!!

This is the reason why I keep doing almost every SymfonyCasts tutorials. Even though I'm very familiar with Doctrine, I did not know that trick! It made my day!

Keep it up, friends!

1 |

MolloKhan SFCASTS julien_bonnier 3 years ago edited

You're welcome @julien_bonnier :)

|

vince-amstz 2 years ago edited

Hello there!
I have a question on the SQL functions that we used in this tuto are available because we used in this tutorial beberlei/DoctrineExtensions. But currently, this project is "well blocked" to PHP 8.0 instead of PHP 8.2, and in November PHP 8.3.

Has anyone found a solution to this? I searched on packagist and github and found nothing maintained.

Should I switch to native SQL queries to be on the safe side for the future on long-term projects? But you lose the object ...

|

MolloKhan SFCASTS vince-amstz 2 years ago edited

Hey @vince-amstz

This tutorial was built on PHP 8.1, and I assume it should work with 8.2 too. Anyways, I noticed that DoctrineExtensions library added support for PHP 8.2 https://github.com/beberlei/DoctrineExtensions/commit/7cfeb9ce1265f43d5007362d0ef9f7c9c68015ef.
Did you get a problem trying to use it in your project?

Cheers!

|

vince-amstz MolloKhan 2 years ago

Yes, you're right, it works. I thought PHP was in 8.0 on the tutorial and that's why it worked.

I had this question just before using it in another project, I saw the commit you sent but also that the last relase was 3 years old and supported PHP 8.0
https://github.com/beberlei/DoctrineExtensions/releases/tag/v1.3.0

Am I missing something?

|

MolloKhan SFCASTS vince-amstz 2 years ago edited

Oh, yea, you're looking at version 1.3.0, they are still active but it seems like they have not released any new version yet, they have been committing everything to master https://github.com/beberlei/DoctrineExtensions/commits/master
I don't know the reason but perhaps you could open a ticket in the repository

1 |

Sidi-LEKHAIFA 2 years ago edited

hello,
I have a question regarding the use of aliases for the DTO, I'm trying to do this, except that for each entity I have the name field that I want to hydrate the DTO with this, but I can't do it!

$qb
            ->select(
                  sprintf(
                    'NEW %s(
                        c.id,
                        c.email,
                        p.name,
                        m.name,
                        so.name
                    )',
                    OneCustomerBODTO::class
                )
            )
            ->leftJoin('c.partenaire', 'p')
            ->leftJoin('c.medium', 'm')
            ->leftJoin('c.sourceOrigin', 'so');
            // ...otherCode

AND when I try to do this, I get an error, if someone could help me please

$qb
            ->select(
                  sprintf(
                    'NEW %s(
                        c.id,
                        c.email,
                        p.name as partenaire,
                        m.name as medium,
                        so.name as source
                    )',
                    OneCustomerBODTO::class
                )
            )
            ->leftJoin('c.partenaire', 'p')
            ->leftJoin('c.medium', 'm')
            ->leftJoin('c.sourceOrigin', 'so');
            // ...otherCode

Error message :
[Syntax Error] line 0, col 587: Error: Expected Doctrine\\ORM\\Query\\Lexer::T_CLOSE_PARENTHESIS, got 'as'

|

Victor SFCASTS Sidi-LEKHAIFA 2 years ago edited

Hey @Sidi-LEKHAIFA ,

Hm, tricky case... you can try to remove that as keyword, it should be option in SQL, so writing field aliases as p.name AS partenaire and p.name partenaire are both valid. Maybe it might work this way... but I think it will not work either because seems that does not support aliases at all. If so, the only possible solution is to name the field in the DB to make it unique. That will not be ideal, but still a valid workaround.

But even with duplicated column names, I suppose it should still work? Did you try to use it without aliases? Is "partenaire" overridden by "medium" and then by "source"? IIRC that should pass fields to arguments by ordinal numbers.

Cheers!

|

Sidi-LEKHAIFA Victor 2 years ago

Hello @Victor,
in fact, renaming fields doesn't seem very sensible to me, since I use these fields in a lot of places.

I thought it would overload the values since they'd have the same aliases, but no, it works perfectly, so I don't need the aliases.

Thank you very much

|

Victor SFCASTS Sidi-LEKHAIFA 2 years ago edited

Hey @Sidi-LEKHAIFA

Perfect! Yeah, that's how it's supposed to work I think. And thanks for confirming it works without overrides :)

Cheers!

|

seb-jean 2 years ago

Hello,
Great this video :).

In my query I have both a select() and an addSelect(). How could I do to have this New DTO Object system?

|

Victor SFCASTS seb-jean 2 years ago edited

Hey @seb-jean ,

I think you need to rewrite your logic into a single select(), i.e. prepare everything you need before the select() and use it there :)

Cheers!

|

seb-jean Victor 2 years ago

Thanks Victor

|

Sidi-LEKHAIFA 3 years ago

It's really great this way, do you know if it only works if the DTO hydrates through the constructor or if the DTO can hydrate through the getters and setters?

|

MolloKhan SFCASTS Sidi-LEKHAIFA 3 years ago edited

Hey @Sidi-LEKHAIFA

That's a good question. I believe Doctrine does not support setter methods. They are not explicit about it in the docs though https://www.doctrine-project.org/projects/doctrine-orm/en/latest/reference/dql-doctrine-query-language.html#new-operator-syntax
I'd just give it a try to confirm it

Cheers!

1 |

Sidi-LEKHAIFA MolloKhan 3 years ago edited

Thanks @MolloKhan for your answer, yes I confirm that it doesn't work with setters, I just tried it. but it's good to know

1 |

This tutorial is built on Symfony 6 but works great on Symfony 7 & 8!

Symfony 6 Doctrine 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.2",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "beberlei/doctrineextensions": "^1.3", // v1.3.0
        "doctrine/doctrine-bundle": "^2.7", // 2.9.1
        "doctrine/doctrine-migrations-bundle": "^3.2", // 3.2.2
        "doctrine/orm": "^2.13", // 2.15.1
        "symfony/asset": "6.2.*", // v6.2.7
        "symfony/console": "6.2.*", // v6.2.10
        "symfony/dotenv": "6.2.*", // v6.2.8
        "symfony/flex": "^2", // v2.2.5
        "symfony/framework-bundle": "6.2.*", // v6.2.10
        "symfony/proxy-manager-bridge": "6.2.*", // v6.2.7
        "symfony/runtime": "6.2.*", // v6.2.8
        "symfony/twig-bundle": "6.2.*", // v6.2.7
        "symfony/webpack-encore-bundle": "^1.16", // v1.16.1
        "symfony/yaml": "6.2.*" // v6.2.10
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.4", // 3.4.4
        "symfony/maker-bundle": "^1.47", // v1.48.0
        "symfony/stopwatch": "6.2.*", // v6.2.7
        "symfony/web-profiler-bundle": "6.2.*", // v6.2.10
        "zenstruck/foundry": "^1.22" // v1.32.0
    }
}

Previous Challenge

Next Challenge