Symfony4中Doctrine映射异常排查（实体类已存在）

Hey there! Let's break down the issues in your code that are causing the Doctrine mapping exception and other related problems. I'll go step by step so you can fix them easily.

1. Missing Join Column Configuration in ManyToOne Association #

Your Professionnel entity's $coordonnees property uses @ManyToOne but doesn't explicitly define the join column. While Doctrine tries to auto-generate this, explicit configuration avoids mapping inconsistencies (especially since your other entities work fine—they likely have this setup).

Fix: Update the annotation in your Professionnel entity:

/**
 * @ORM\ManyToOne(targetEntity="App\Entity\Coordonnees")
 * @ORM\JoinColumn(name="coordonnees_id", referencedColumnName="id", nullable=true)
 */
private $coordonnees;

nullable=true is optional—adjust it if you want to enforce that every Professionnel must have associated Coordonnees.

2. Repository Method Doesn't Return Results #

Your getProEtAdresses() method in ProfessionnelRepository executes the SQL but doesn't return any data. This will cause your controller to receive null instead of the expected array, leading to errors when rendering the view.

Fix: Add a return statement to fetch the results. If you want raw database rows:

public function getProEtAdresses(): array {
    $conn = $this->getEntityManager()->getConnection();
    $sql = ' SELECT * FROM coordonnees INNER JOIN `professionnel` ON `professionnel`.`coordonnees_id`= `coordonnees`.`id` ';
    $stmt = $conn->prepare($sql);
    $stmt->execute();

    // Return results as an associative array
    return $stmt->fetchAllAssociative();
}

Or, for fully hydrated Doctrine entities (more aligned with Symfony/Doctrine best practices):

public function getProEtAdresses(): array {
    return $this->createQueryBuilder('p')
        ->innerJoin('p.coordonnees', 'c')
        ->addSelect('c')
        ->getQuery()
        ->getResult();
}

This gives you Professionnel objects with their linked Coordonnees already loaded, avoiding mapping issues from raw SQL.

3. Typo in Controller Method Call #

In your ProfessionnelsController, you're calling getProEtAdresse() (singular) but your repository method is named getProEtAdresses() (plural). This throws a "method not found" exception that might be getting mixed up with the mapping error.

Fix: Correct the method name in your controller:

$ListeProEtAdresse = $this->getDoctrine()
    ->getRepository(Professionnel::class)
    ->getProEtAdresses(); // Add the missing 's'

4. Incorrect Usage of find() in Detail Action #

In your detailProfessionnels method, you're passing a Coordonnees object (or null) to find(), which expects an ID value. This will cause an error when trying to fetch the address.

Fix: You don't need to re-fetch Coordonnees—use the associated object directly from the Professionnel entity:

public function detailProfessionnels($id) {
    $Pro = $this->getDoctrine()
        ->getRepository(Professionnel::class)
        ->find($id);

    // Access the linked Coordonnees directly
    $Coordonnees = $Pro->getCoordonnees();

    // Complete the render call with your template path
    return $this->render('GestionASM17/detail_professionnel.html.twig', [
        'pro' => $Pro,
        'coordonnees' => $Coordonnees
    ]);
}

Final Step: Clear Doctrine Cache #

After making these changes, clear Doctrine's metadata cache to ensure the updated mappings are picked up:

php bin/console doctrine:cache:clear-metadata
php bin/console cache:clear

These fixes should resolve the mapping exception and other related issues in your code. Let me know if you hit any other snags!

内容的提问来源于stack exchange，提问作者Yot