Hazte profesional con las consultas de Doctrine

Hey @Eric-N!

Good question! This tutorial is all about Doctrine, but we are absolutely working inside of Symfony. So the directory structure, bin/console commands (e.g. to generate migrations), and more will not translate. So, while I think you can still learn a lot about Doctrine in this course, you'll definitely need to do some translating to how that looks and works outside of Symfony. If you have any questions along the way, we'd be happy to do our best to answer them :).

Cheers!

Hey Lionel,

Unfortunately, no. But it should be the same DQL query in another DQL, this should work. But subqueries are mostly bad idea, sometimes it might be better (much better performance) to execute 2 separate queries. If you use subqueries - I would recommend you to profile those queries to see how long they are executing, then rewrite logic with 2 queries and compare. I bet in most cases 2 separate queries will be faster.

Cheers!

The article is quite interesting. But try https://api-platform.com/docs/core/serialization/#embedding-relations . Probably you will achieve the same. If not, you would probably have to look at Doctrine and the Eager Loading. But I have to admit that in my first project with API Platform I encountered an unfavorable combination, combined with quite interesting bugs that e.g. made a difference on which platform the project was built... So I am not completly sure...

Thank you for your answer, do you have an example, or a link that shows the use of Eager Loading?

In combination with API-Platform it is explained here: https://api-platform.com/docs/core/performance/#eager-loading. There are multiple ways.

But I don't see an example for fetching an embedded relation one time with, and another without an eager collection, depending on the route.

For example you have customers with invoices, and each invoice has many products on it.
If you want to show an overview of the invoices you want to show all invoices and a number of positions, but not the product Detail-Data.
But if you want to show an invoice you want to show the invoices with the product data.
I think in this case, you can create a second getter, giving the exact same relation with another name and wihtout eager loading. In combination with https://api-platform.com/docs/core/serialization/#embedding-relations > Normalization Groups ( #[Groups('book')] ) even this should be possbile.