Challenge 2 / 2

After upgrading to Doctrine Bundle 3 (native lazy objects), you mark Starship as final. Later, you add a custom method getDisplayName() to Starship and use it like $part->getStarship()->getDisplayName() in a template. When does Doctrine actually hit the database to load the starship’s other fields?

When Symfony renders the template, it automatically “warms up” every lazy relation to avoid surprises.

Only when getDisplayName() touches a real field (like $this->name) or calls another getter that needs it.

It loads the Starship fully as soon as you call getStarship(), even if you don’t read any data from it.

Right when you call $repository->find(1), Doctrine always loads the whole Starship immediately.

Rewatch the video