Download the PHP package lexiphanic/doctrine-rest-driver without Composer
On this page you can find all versions of the php package lexiphanic/doctrine-rest-driver. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 doctrine-rest-driver
Motivation
The CircleOfNice DoctrineRestDriver was a great starting point for a solution I required, however I found a couple of bugs so natually went to try and fix them but instead I found it difficult to follow and slightly confusing so ended up ripping it apart to A) fix the bugs, and B) learn more about the Doctrine DBAL
Prerequisites
- This repo, ideally via composer
- PHP 5.5 or later
Installation
Add the driver to your project using composer:
Change the following doctrine dbal configuration entries:
The CircleOfNice has lots of options that allow you to set various CURL options however they are not the concern of this project. This is the reason there are no futher options. So if you want to alter the requests, responses or transformers, then you can use middlewares in Guzzle for example or create your own transformer.
Usage
If your API routes follow these few conventions, using the driver is very easy:
- Each route must be structured the same:
- If there is an
idcolumn, this will be appended - If the response is an array which only has an array eg then it is treated as a result with many rows, row 1 is , row 2 is and so on, otherwise it is treated as a single resultset eg (this is because name is not an array) will return one row that has , and as properties
- Select requests will look like this;
- where the SQL was
- where the SQL was ;
- Delete requests follow the same convention as Select requests, but with the verb ofcourse
- Insert requests will look like this;
- the body of the request will be json encoded pairs (see the Select request for examples on how they're created)
- Update requests are like Select and and Insert requests, like this;
- uri and querystrings follow the same convention as Select requests and the body will be the same as Insert requests
- All requests will use have the following appended if they exist on the SQL
- will append ( and will be typecasted to )
- will append
If this is not the case, you can ofcourse use an alternative transformer, extend this transformer or add Guzzle middleware.
