Zend Framework ORM 风格的表数据网关与扩展 Zend_Db_Table_Abstract-php问题

Zend Framework ORM-style table data gateway vs. extending Zend_Db_Table_Abstract(Zend Framework ORM 风格的表数据网关与扩展 Zend_Db_Table_Abstract)

本文介绍了Zend Framework ORM 风格的表数据网关与扩展 Zend_Db_Table_Abstract的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

在 Zend 框架快速入门中，从将 Zend_Db_Table_Abstract 扩展到表数据网关模式的模型发生了变化.

In the Zend Framework Quickstart, there has been a change from models that extend Zend_Db_Table_Abstract to the Table Data Gateway pattern.

就我个人而言，我对这种模式没有太多经验，我一直听说最有可能使用这种模式而不是旧方式.

Personally, I have not had much experience with this pattern and I keep hearing this should most likely be used instead of the old way.

快速入门中的一个简短示例:

老方法:

class Default_Model_Guestbook extends Zend_Db_Table_Abstract
{
    protected $_name = 'tablename';

    // do stuff
}

新方法:

// The actual model
class Default_Model_Guestbook
{
    protected $_comment;
    protected $_created;
    protected $_poster;
    // list continues with all columns
}

// Dbtable for this model
class Default_Model_DbTable_Guestbook extends Zend_Db_Table_Abstract
{
    /** Table name */
    protected $_name    = 'guestbook';
}

// Mapper 
class Default_Model_GuestbookMapper
{
    public function save($model);
    public function find($id, $model);
    public function fetchAll();
}

由于我对这种编程风格缺乏经验，我发现很难掌握后一种方式的实际好处；我知道这种方法尽可能地将数据库与实际逻辑分开，理论上这应该可以更容易地过渡到另一个数据库平台.但是，我真的没有看到这种情况发生在我正在工作的任何项目中.

From my lacking experience with this style of programming, I find it hard to grasp the actual benefits from this latter way; I understand that this method seperates the database from the actual logic as much as possible, which should in theory make a transition to another database platform easier. However, I really don't see this happening on any project I am working.

毫无疑问，我忽略了一些东西，所以我很想听听你的建议.

There is almost no doubt that I am overlooking something, so I'd love to hear your advice.

问题: