Currently, I am in the process of importing users from an excel file. To manage this task effectively, I have established an entity manager:
$em = $this->getDoctrine()->getManager();
Here is a snippet of the loop I am using for this operation:
...
for ($i=2; $i<=count($usersdatas); $i++) { // $userdatas: an array of users imported from excel
$nuser = new User();
$nuser->setEmail($usersdatas[$i]['A']); // email is unique in db
$nuser->setFname($usersdatas[$i]['B']);
$nuser->setLname($usersdatas[$i]['C']);
$nuser->addChannel($channel); //ManytoMany relation
$em->persist($nuser);
$em->flush();
}
...
- The Email field holds unique values in the database and I prefer not to check for duplicates before flushing (database validation).
- I choose to flush entities one by one for logging purposes (not batch insertion).
- All other codes and files including entities, services, configurations are free of errors.
Initially, I faced issues when attempting to handle duplicate emails during the import process. However, I resolved this issue by implementing the following adjustment:
...
try {
$em->persist($nuser);
$em->flush();
} catch (\Exception $e) {
...
}
...
Another challenge emerged in the form of "The EntityManager is closed" exception. This occurred if a duplicate email was detected, causing the automatic closure of the EntityManager ($em). To tackle this problem, I generated a new $em instance before the try/catch block:
...
if (!$em->isOpen()) {
$em = $em->create(
$em->getConnection(), $em->getConfiguration());
}
...
While these adjustments have helped resolve previous issues, I encountered difficulties when trying to associate a channel with a user:
...
$nuser->addChannel($channel); //ManytoMany relation
...
In this scenario, $channel is an existing entity. Despite this, post recreating EntityManager, it is treated as a new entity at the time of persisting, resulting in the mentioned error message:
ORMInvalidArgumentException {#1400 ▼
#message: "A new entity was found through the relationship 'My\UserBundle\Entity\User#channels' that requires cascade persist operations for entity..."
#code: 0
#file: "...\vendor\doctrine\orm\lib\Doctrine\ORM\ORMInvalidArgumentException.php"
#line: 91
-trace: array:13 [▶]
}
The challenges I am facing seem to be linked to the recreation of EntityManager. It appears to be causing unexpected behavior within the system. Closing the EntityManager post encountering database errors restricts our ability to communicate effectively with the database after such occurrences.
With this context in mind, I pose two questions:
- Is there a method available to prevent the automatic closure of EntityManager?
- Would utilizing DBAL Doctrine be a viable alternative for importing users, particularly those with potentially duplicated emails?