Download the PHP package 3ie/laravel-storedprocedures without Composer
On this page you can find all versions of the php package 3ie/laravel-storedprocedures. 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 laravel-storedprocedures
Laravel stored procedures
This package allow you to work with PostgreSQL stored procedures with Laravel 5. It allows you to generate models to simply use your procedures in your PHP code.
Installation
Package installation
With Composer
Require this package by adding following dependency on your composer.json
Then update composer with composer update or composer install.
With Laravel bundle
If you do not want to use Composer, you can install it by using Laravel Bundle by typing this command
Registering service provider
Once the package is installed, add the ServiceProvider in providers array on app/config/app.php :
Usage
You can generate model for your stored procedures (aka functions) by typing this command
Only stored procedures which name start with sp_ will have a model generated, other ones will be ignored.
Models will be written in app/store_procedures directory (or the one defined in configuration file). Do not edit these models ! They will be overwritten at next generation.
Configuration
You have to run the vendor:publish method to copy the configuration file into you app directory
You can change the database schema to read and the directory where models for stored procedures are written. You can also modify the namespace used for your sp_models
Models
Generated models have an execute() methods that allow you to execute stored procedure and get result (if the procedure returns one) from it.
If procedure have IN or INOUT parameter, the execute() method will have the same parameter in the same order.
If it has OUT or INOUT parameter, model will have an attribute with getter/setter for every OUT parameters.
Setters will not modify data, they are only present to allow you to format data if you want to use it on views by uysing whole model instead of simple variables.
Example
Giving the following stored procedure, that retrieve all friends of a user giving its id...
...we will have a SP_Getfriends class generated. We can use it like this :
