Enable your models to regularly cut/copy & paste their data into another table.
- Cut & Paste or Copy & Paste
- Scheduled Jobs available to regularly & asynchronously run
- Cut & Paste in chunks, to split potential long-running processes
- Store data e.g. into logging or daily tables and keep the production data clean
You can install the package via composer:
composer require elipzis/laravel-pastable-modelYou can publish the config file with:
php artisan vendor:publish --tag="pastable-model-config"This is the contents of the published config file:
return [
//The default cut&paste chunk size (limit)
'chunkSize' => 1000,
//Auto-create tables, if not existing
'autoCreate' => false,
//Enable detailed logging to any accepted and configured level
'logging' => [
'enabled' => false,
'level' => null,
],
];To make your model copy & pastable, add the trait CopyPastable.
It will copy & paste your configured query result into the target table.
...
use ElipZis\Pastable\Models\Traits\CopyPastable;
...
class YourModel extends Model {
use CopyPastable;
...To make your model cut & pastable, add the trait CutPastable.
It will cut (delete) & paste your configured query result into the target table.
If more rows than the chunk size (limit) are affected, it will respawn its own job until completed.
...
use ElipZis\Pastable\Models\Traits\CutPastable;
...
class YourModel extends Model {
use CutPastable;
...To use any trait, you need to configure two settings:
- the target table
- the query to read its data from
You must define the target table name.
...
class YourModel extends Model {
...
protected string $pastableTable = 'log_something';
...or by overriding the getter function, to e.g. create dynamic table names
...
class YourModel extends Model {
...
public function getPastableTable(): string
{
return 'log_something_' . Carbon::now()->format('Y_m_d');
}
...If the table does not exist, you can use the configuration setting autoCreate and set it to true to have the system
try to create the table from your query source.
It is recommended for you to create the table manually or via migration, as the automation is not fully tested and functional to any database system and table structure.
You must define the query to use to read data and cut/copy & paste into the target table.
...
class YourModel extends Model {
...
public function getPastableQuery(): Builder
{
return static::query()->where('created_at', '<=', now()->subDay());
}
...You can use any query that returns a Builder object.
In the case of cut & paste, the default chunkSize is used as a limiter. You can set your own limit by
adding ->limit() to the query or override the configuration setting in general.
You can give a separate connection if you want the target table to be generated and filled in e.g. another database.
...
class YourModel extends Model {
...
protected string $pastableConnection = 'logging';
...After implementation and configuration, you got three options to trigger the cut/copy & paste jobs:
- Manually dispatching the jobs
- Scheduled dispatch
- Running a command to trigger it manually
The preferred way is to run the job on a schedule, configured via the Kernel, e.g. daily:
namespace App\Console;
...
use ElipZis\Pastable\Jobs\PastableJob;
...
class Kernel extends ConsoleKernel
...
protected function schedule(Schedule $schedule)
{
...
$schedule->job(PastableJob::class)->daily();
...
}
...You may also trigger the execution manually by using the command(s):
- All cut/copy & pastable model classes:
php artisan pastable:all - Only copy & pastable model classes:
php artisan pastable:copy - Only cut & pastable model classes:
php artisan pastable:cut
The final option is to trigger the job manually inside any of your functions, any logic, any application code:
...
use ElipZis\Pastable\Jobs\PastableJob;
...
class YourClass
...
protected function yourFunction()
{
...
PastableJob::dispatch();
...
}
...composer testThis package is heavily inspired by two incredible resources:
Kudos and Thanks to both for the inspiration.
Please see CHANGELOG for more information on what has changed recently.
Please see CONTRIBUTING for details.
Please review our security policy on how to report security vulnerabilities.
The MIT License (MIT). Please see License File for more information.