| Package Data | |
|---|---|
| Maintainer Username: | davelip |
| Maintainer Contact: | lippi.david@gmail.com (David Lippi) |
| Package Create Date: | 2014-11-19 |
| Package Last Update: | 2018-08-27 |
| Language: | PHP |
| License: | MIT |
| Last Refreshed: | 2025-10-31 03:05:04 |
| Package Statistics | |
|---|---|
| Total Downloads: | 90,958 |
| Monthly Downloads: | 319 |
| Daily Downloads: | 10 |
| Total Stars: | 22 |
| Total Watchers: | 3 |
| Total Forks: | 12 |
| Total Open Issues: | 0 |
This is a real queue driver, like beanstalkd or redis one. You need a daemon like supervisor or similar to listen to your queue.
Add the package to the require section of your composer.json and run composer update
"davelip/laravel-database-queue": ">0.5"
Add the Service Provider to the providers array in config/app.php
'Davelip\Queue\DatabaseServiceProvider'
I suggest to publish migrations, so they are copied to your regular migrations
$ php artisan migrate:publish davelip/laravel-database-queue
And then run migrate
$ php artisan migrate
I suggest to create the failed_jobs table, in this moment, with:
$ php artisan queue:failed-table
You should now be able to use the database driver in config/queue.php
'default' => 'database',
'connections' => array(
...
'database' => array(
'driver' => 'database',
'queue' => 'queue-name', // optional, can be null or any string
'lock_type' => 0, // optional, can be 0, 1 or 2
),
...
}
It work in the same as beanstalkd or redis queue listener.
Listen for new job:
$ php artisan queue:listen
Concurrency are managed by status column in the queues table, so you can parallelize your queue:listen.
Atomicity of status change are garantee by database transaction, if you are having problems of race condition
can You set the option lock_type to:
see http://laravel.com/docs/4.2/queries#pessimistic-locking for further info.
For more info see http://laravel.com/docs/queues
Loosely based on https://github.com/barryvdh/laravel-async-queue