gridonic/repository-service-provider
Composer 安装命令:
composer require gridonic/repository-service-provider
包简介
Doctrine repository service provider for Silex
关键字:
README 文档
README
This service provider exposes an easy way to have Repositories for your silex database.
Requirements
This service provider has ben built to work with the DoctrineServiceProvider silex extension. See Silex' DoctrineServiceProvider documentation for instruction on how to use it.
Configuration
Add the the repository to your dependencies, then register the autoload:
$app['autoloader']->registerNamespaces(array(
/** Your other namespaces **/
'Knp' => __DIR__.'/../vendor/KnpSilexExtensions/'
));
Register the service provider:
$app->register(
new Knp\Provider\RepositoryServiceProvider(), array(
'repository.repositories' => array(
'projects' => 'MyProject\Repository\Project',
)
)
);
The service provider expects parameter repository.repositories to be set and to be an associative array with service names as keys and repository classes as values.
In the example above, the projects service will be exposed by Pimple (ie, you can access it through $app['projects']) using the MyProject\Repository\Project class.
Usage
As you might have guessed by now, you need to implement a concrete class for every repository that you want to use. That repository must extend Knp\Repository and implement the getTableName method, that should return the database's table name bound to that repository.
In the example above, given your projects are stored in the project table, the MyProject\Repository\Project class would look like that:
<?php
namespace MyProject\Repository;
use Knp\Repository;
class Project extends Repository;
{
public function getTableName()
{
return 'project';
}
}
The default repository implementation exposes a number of methods to manipulate your database that are basically proxies to methods from Doctrine\DBAL\Connection:
insert(array $data)
$app['projects']->insert(array(
'title' => 'foo',
'description' => 'A project'
));
Will insert a project in the table with title "foo" and description "A project".
update(array $data, array $identifier)
$app['projects']->update(array('title' => 'bar'), array('title' => 'foo'));
Will update all projects' title from "foo" to "bar".
delete(array $identifier)
$app['projects']->delete(array('title' => 'bar'));
Will update all projects which title is "bar".
find($id)
$app['projects']->find(42);
Returns the project which primary key is 42.
findAll()
$app['projects']->findAll();
Returns the entire table content.
Extending a repository
Extending a repository is as easy as adding methods to it. For example, you could add a findByTitle($title) method to return all projects based on their title:
public function findByTitle($title)
{
return $this->db->fetchAll('SELECT * FROM project WHERE title = ?', array($title));
}
Credits
- KnpLabs for original code
- Joshua Morse for initial code extraction
gridonic/repository-service-provider 适用场景与选型建议
gridonic/repository-service-provider 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 141 次下载、GitHub Stars 达 0, 最近一次更新时间为 2014 年 10 月 21 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「silex」 「repository」 「doctrine2」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 gridonic/repository-service-provider 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 gridonic/repository-service-provider 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 gridonic/repository-service-provider 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
repository php library
An extension of ScnSocialAuth that provides integration with Doctrine2 ORM.
Doctrine2 behavior traits - slowhop fork
Object-oriented CRUD for Doctrine DBAL
Laravel 5 - Repositories to the database layer
Command bus implementation: Commands and domain events
统计信息
- 总下载量: 141
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 3
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2014-10-21