我使用 symfony 2.3 和 php doctrine 2。

程序有以下模型:

• 实体订单 - 典型的客户订单
• entity BadOrderEntry(fields: id, order - 与 Order, createdAt 的单向一对一关系)
• 用于创建实体 BadOrderEntry 的工厂 BadOrderEntryFactory
• 存储库 BadOrderEntryRepository 用于实体 BadOrderEntry 的搜索方法
• 管理器 BadOrderEntryManager，用于保存/编辑/删除实体 BadOrderEntry 的方法

• AND MAIN CLASS BadOrderList - 不良订单列表，此类代码:

  private $factory;
  private $repository;
  private $manager;
  
  public function __construct(
      BadOrderEntryFactory $f,
      BadOrderEntryRepository $r,
      BadOrderEntryManager $m
  ) {
      $this->factory = $f;
      $this->repository = $r;
      $this->manager = $m;
  }
  
  public function has(Order $order)
  {
      return $this->repository->existsByOrder($order);
  }
  
  public function add(Order $order)
  {
      if (! $this->has($order)) {
          $entry = $this->factory->create($order);
          $this->manager->save($entry);
      }
  }
  
  public function remove(Order $order)
  {
      $entry = $this->repository->findOneByOrder($order);
      if ($entry !== null) {
          $this->manager->delete($entry);
      }
  }
  

我很喜欢这个类(class)的设计。我想了很多。 一切都很棒。但!存在一个问题:add 和 remove 方法中的操作必须在事务中执行。

PHP Docrine 2 中的事务代码如下所示:

<?php
$em->getConnection()->beginTransaction();
try {
    //... do some work
    $em->getConnection()->commit();
} catch (Exception $e) {
    $em->getConnection()->rollback();
    throw $e;
}

但是我如何在 BadOrderList 中调用这段代码呢？

我花了很多时间删除依赖数据库(以及相应的 PHP Doctrine 2)，然后重新创建它？ 现在依赖隐藏在类 BadOrderEntryRepository 和 BadOrderEntryManager 中。

如何在类BadOrderList中隐藏对交易机制的依赖？

最佳答案

经过我们的讨论，我对您的问题有了答案。 问题实际上不是“如何隐藏对类 BadOrderList 中事务机制的依赖？”，而是如何将模型与持久层分离？(Doctrine2 在那特殊情况)。

我试着用一些代码来说明我的建议

class BadOrderEntry
// Bad - is too bad word to describe an order here. Why is it bad? Is it Declined? Cancelled?
{
   private $order;
   // some code
}
class BadOrderEntryFactory 
{ 
   // If there is not to much processing to build BadOrderEntry better use factory method like BadOrderEntry::fromOrder($order); 
}
class BadOrderEntryRepository 
{ 
   // here is some read model 
}
class BadOrderEntryManager  
// ITS a part of our model and shouldn't be coupled to ORM
{
  public function save(BadEntry $be) 
  {
    // some model events, model actions
    $this->doSave($be); // here we should hide our storage manipulation
  }

  protected function doSave($be) // it can be abstract, but may contain some basic storage actions  
  { 
  }

  // similar code for delete/remove and other model code
}
class ORMBadOrderEntryManager extends BadOrderEntryManager 
// IT'S NOT the part of your model. There is no business logic. There is only persistent logic and transaction manipulation
{ 
  protected $entityManager;

  // some constructor to inject doctrine entitymanager

  protected doSave($be)
  {
    $em = $this->entityManager;
    $em->getConnection()->beginTransaction(); // suspend auto-commit
    try {
      $em->persist($be);
      $em->flush();
      $em->getConnection()->commit();
    } catch (Exception $e) {
      $em->getConnection()->rollback();
      throw $e;
    }
  }
}
// You can also implement ODMBadOrderEntryManager, MemcacheBadOrderEntryManager etc.

因此，如果我们谈论目录结构，您的所有模型都可以从 bundle 中移出并在任何地方使用。您的 Bundle 结构如下:

BadEntryBundle
|
+ Entity
| |
| --- BadOrderEntryEntity.php
|
+ ORM
| |
| --- ORMBadOrderEntryManager.php 

然后您只需将 ORMBadOrderEntryManager 注入(inject) BadOrderEntryList

关于php - 将业务逻辑与 PHP Doctrine 2 分开，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/27766476/