Symfony 3 查询开发求助：匹配验证后插入数据逻辑实现

Hey there! As someone who’s stumbled through early Symfony/Doctrine hurdles myself, I totally get where you’re stuck. Let’s walk through a clean, Symfony-best-practice solution for your requirement step by step.

First, I’ll assume you’re using Doctrine (Symfony’s default ORM) since that’s standard for database operations. Let’s break this into manageable parts:

1. Ensure Your Entity is Set Up Correctly #

Make sure you have an entity class mapped to your target table (let’s call it Verification for example, replace with your actual table name). It should have the id and code fields properly annotated:

// src/Entity/Verification.php
namespace App\Entity;

use Doctrine\ORM\Mapping as ORM;

#[ORM\Entity(repositoryClass: VerificationRepository::class)]
class Verification
{
    #[ORM\Id]
    #[ORM\GeneratedValue]
    #[ORM\Column(type: 'integer')]
    private ?int $id = null;

    #[ORM\Column(type: 'string', length: 255)]
    private ?string $code = null;

    // Getters and setters (generate these with `php bin/console make:entity` if you haven't already)
    public function getId(): ?int
    {
        return $this->id;
    }

    public function getCode(): ?string
    {
        return $this->code;
    }

    public function setCode(string $code): self
    {
        $this->code = $code;
        return $this;
    }
}

2. Create a Custom Repository Method (Optional but Recommended) #

For cleaner code, wrap your query logic in a custom repository method instead of writing it directly in the controller:

// src/Repository/VerificationRepository.php
namespace App\Repository;

use App\Entity\Verification;
use Doctrine\Bundle\DoctrineBundle\Repository\ServiceEntityRepository;
use Doctrine\Persistence\ManagerRegistry;

class VerificationRepository extends ServiceEntityRepository
{
    public function __construct(ManagerRegistry $registry)
    {
        parent::__construct($registry, Verification::class);
    }

    // Custom method to find by id + code
    public function findMatching(int $userId, string $userCode): ?Verification
    {
        return $this->createQueryBuilder('v')
            ->andWhere('v.id = :userId')
            ->andWhere('v.code = :userCode')
            ->setParameter('userId', $userId)
            ->setParameter('userCode', $userCode)
            ->getQuery()
            ->getOneOrNullResult();
    }
}

3. Implement the Logic in Your Controller #

Now wire everything together in a controller method. We’ll check for the matching record, run the insert if found, or return an error if not:

// src/Controller/YourController.php
namespace App\Controller;

use App\Entity\YourTargetEntity; // Replace with the entity you want to insert into
use App\Repository\VerificationRepository;
use Doctrine\ORM\EntityManagerInterface;
use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
use Symfony\Component\HttpFoundation\Response;

class YourController extends AbstractController
{
    public function processRequest(int $userId, string $userCode, VerificationRepository $verificationRepo, EntityManagerInterface $em): Response
    {
        // 1. Check for matching id and code
        $matchingRecord = $verificationRepo->findMatching($userId, $userCode);

        if ($matchingRecord) {
            // 2. Match found: execute insert operation
            $newEntity = new YourTargetEntity();
            $newEntity->setUserId($userId); // Set your required fields here
            // $newEntity->setOtherField('value');

            $em->persist($newEntity);
            $em->flush();

            // Return success response (adjust format to your needs: JSON, Twig template, etc.)
            return $this->json([
                'status' => 'success',
                'message' => 'Data inserted successfully'
            ]);
        } else {
            // 3. No match: return error
            return $this->json([
                'status' => 'error',
                'message' => 'Invalid ID or code provided'
            ], Response::HTTP_BAD_REQUEST);
        }
    }
}

• Double-check your entity mappings: Make sure the id and code fields in your entity match the exact column names and types in your database.
• Use parameter binding: The example uses query builder parameters to avoid SQL injection — never concatenate user input directly into queries!
• Adjust response format: If you’re not using JSON, you could use flash messages and redirect to a template instead:

  $this->addFlash('error', 'Invalid ID or code');
  return $this->redirectToRoute('your_route_name');
  

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