Download the PHP package proai/eloquent-versioning without Composer
On this page you can find all versions of the php package proai/eloquent-versioning. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package eloquent-versioning
Eloquent Versioning
This is an extension for the Eloquent ORM to support versioning. You can specify attributes as versioned. If an attribute is specified as versioned the value will be saved in a separate version table on each update. It is possible to use timestamps and soft deletes with this feature.
Installation
Eloquent Versioning is distributed as a composer package. So you first have to add the package to your composer.json
file:
Then you have to run composer update
to install the package.
Example
We assume that we want a simple user model. While the username should be fixed, the email and city should be versionable. Also timestamps and soft deletes should be versioned. The migrations would look like the following:
The referring Eloquent model should include the code below:
Usage
Database Tables
You need to add the following columns to your main model table:
latest_version
(integer).
Furthermore you need a version table. The name of the version table is identical with the name of the main model table (e. g. for a model table users
the name would be users_version
). This table must contain the following columns:
ref_
followed by the name of the model's primary key (if the primary key isid
, the column name will beref_id
)version
(integer)
Eloquent Models
You have to define a $versioned
array in your model that contains all versioned columns.
Database Queries
Query the database
By default the query builder will fetch the latest version (e. g. User::find(1);
will return the latest version of user #1). If you want a specific version or all versions, you can use the following:
-
version(VERSION_NO)
returns a specific version
Example:User::version(2)->find(1)
will return version #2 of user #1 -
allVersions()
returns all versions of the queried items
Example:User::allVersions()->get()
will return all versions of all users moment(Carbon)
returns a specific version, closest but lower than the input date
Example:User::moment(Carbon::now()->subWeek()->find(1)
will return the version at that point in time.
Create, update and delete records
All these operations can be performed normally. The package will automatically generate a version 1 on create, the next version on update and will remove all versions on delete.
Timestamps
You can use timestamps in two ways. For both you have to set $timestamps = true;
.
-
Normal timestamps
The main table must include acreated_at
and aupdated_at
column. Theupdated_at
column will be overriden on every update. So this is the normal use of Eloquent timestamps. - Versioned timestamps
If you addupdated_at
to your$versioned
array, you need acreated_at
column in the main table and aupdated_at
column in the version table (see example). On update theupdated_at
value of the new version will be set to the current time. Theupdated_at
values of previous versions will not be updated. This way you can track the dates of all updates.
Soft Deletes
If you use the Versionable
trait with soft deletes, you have to use the ProAI\Versioning\SoftDeletes
trait from this package instead of the Eloquent soft deletes trait.
-
Normal soft deletes
Just use adeleted_at
column in the main table. Then on delete or on restore thedeleted_at
value will be updated. - Versioned soft deletes
If you create adeleted_at
column in the version table and adddeleted_at
to the$versioned
array, then on delete or on restore thedeleted_at
value of the new version will get updated (see example). Thedeleted_at
values of previous versions will not be updated. This way you can track all soft deletes and restores.
Custom Query Builder
If you want to use a custom versioning query builder, you will have to build your own versioning trait, but that's pretty easy:
Obviously you have to replace MyVersioningBuilder
by the classname of your custom builder. In addition you have to make sure that your custom builder implements the functionality of the versioning query builder. There are some strategies to do this:
- Extend the versioning query builder
ProAI\Versioning\Builder
- Use the versioning builder trait
ProAI\Versioning\BuilderTrait
- Copy and paste the code from the versioning query builder to your custom builder
Support
Bugs and feature requests are tracked on GitHub.
License
This package is released under the MIT License.