symfony | seamlessly integrate the Backup Manager | Web Framework library

Doctrine uses the identity map

The websocket server is a daemon and all cleanup tasks are the responsibility of the developer

Use

\Doctrine\ORM\EntityManager::find with the $lockMode argument = \Doctrine\DBAL\LockMode::NONE

OR

Call the \Doctrine\ORM\EntityManager::clean method before \Doctrine\ORM\EntityManager::find

You need to configure objectManagerLoader so that the extension can see the entity metadata. This will allow DQL validation, and the correct entity repositoryClass to be inferred when accessing $entityManager->getRepository(). Add to your phpstan.neon:

Sounds like you should run composer global update to update the packages that you've installed globally.

Try to run command netstat -nltp. It shows active addresses and ports. Your nginx process should be run at 0.0.0.0:8000. 0.0.0.0 means the nginx process is available from anywhere.

If your nginx process is ran by any specific ip address, you should access it by that ip address, e.g http://192.168.4.2:8000.

Ok, now im deprecation free but there are some things to now after upgrading from 4.4 to 5.3

To find all warnings I created a new symfony project to compare different files

1. KernelEvent::isMasterRequest()" is deprecated, use "isMainRequest()

   take a look into your file src/Kernel.php - there u can find the deprecated method

2. The "session.storage.factory.service" service is deprecated

   open your framework.yaml and compare with the following code. Maybe it could help you:

Since you have already loaded the entire contents of the spreadsheet into the $validatedFile variable, why make a LazyCollection object? Their only purpose is to save memory by not loading large data sets into memory. Your validation rules using closures can also be cleaned up. This isn't just a cosmetic change: in_array() is notoriously slow.

I got the same problem. Open your terminal and write this:

if your controller extends "AbstractController" you can use $this->getUser() to get the current User.

in your list function you are not giving an user id neither an $user so $user is rationally null

As Yassinefikri explained, the default Symfony behavior is not to request the linked Entities to avoid bad performance.

To solve the problem, you need a proper function in the repository where you will fetch the Clients and join them with their Templates.

This allows to fetch all the Clients without their Template but also be able to fetch all the Clients with their Templates, regarding of if you need it or not.

Changing the default behavior of Symfony by adding a fetch="EAGER" is not good practice, you should always create a function for a desired result instead of changing default behavior (which would decrease performance, specially if you are dealing with a big DB).

- EDIT, Better (and more optimized) way of solving the problem

As Will B said, the behavior comes from Doctrine ORM and not not Symfony (Symfony frequently is used with Doctrine ORM but this applies to ORM in general).

Another (and better) way of achieving the desired result is to initilialize the object (which will fetch linked entities without actually making JOIN requests to the DB - initializeObject()).

TO SUM UP

NEVER use fetch="EAGER" if you can since this is really the work way of dealing with linked entities, it is ay better to use Will B's or Yassinefikri's solution to the problem.