Download the PHP package insolis/repository-service-provider without Composer
On this page you can find all versions of the php package insolis/repository-service-provider. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download insolis/repository-service-provider
More information about insolis/repository-service-provider
Files in insolis/repository-service-provider
Package repository-service-provider
Short Description Doctrine repository service provider for Silex
License MIT
Homepage http://knplabs.com
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package repository-service-provider
Doctrine repository service provider for Silex
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.
Installation
Add insolis/repository-service-provider to your composer.json file.
Configuration
Register the service provider:
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 Insolis\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:
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)
Will insert a project in the table with title "foo" and description "A project".
update(array $data, array $identifier)
Will update all projects' title from "foo" to "bar".
delete(array $identifier)
Will delete all projects which title is "bar".
find($id)
Returns the project which id field is 42.
findAll()
Returns the entire table content.
count()
Returns the count of all records in the table.
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:
Credits
- KnpLabs for original code
- Joshua Morse for initial code extraction
- Gábor Fási for extended maintenance
