Download the PHP package friendsofhyperf/compoships without Composer
On this page you can find all versions of the php package friendsofhyperf/compoships. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download friendsofhyperf/compoships
More information about friendsofhyperf/compoships
Files in friendsofhyperf/compoships
Package compoships
Short Description Hyperf relationships with support for composite/multiple keys.
License MIT
Informations about the package compoships
Compoships
Compoships offers the ability to specify relationships based on two (or more) columns in Hyperf's Model ORM. The need to match multiple columns in the definition of an Eloquent relationship often arises when working with third party or pre existing schema/database.
The problem
Eloquent doesn't support composite keys. As a consequence, there is no way to define a relationship from one model to another by matching more than one column. Trying to use where clauses
(like in the example below) won't work when eager loading the relationship because at the time the relationship is processed $this->team_id is null.
Installation
The recommended way to install Compoships is through Composer
Usage
Using the FriendsOfHyperf\Compoships\Database\Eloquent\Model
class
Simply make your model class derive from the FriendsOfHyperf\Compoships\Database\Eloquent\Model
base class. The FriendsOfHyperf\Compoships\Database\Eloquent\Model
extends the Eloquent
base class without changing its core functionality.
Using the FriendsOfHyperf\Compoships\Compoships
trait
If for some reasons you can't derive your models from FriendsOfHyperf\Compoships\Database\Eloquent\Model
, you may take advantage of the FriendsOfHyperf\Compoships\Compoships
trait. Simply use the trait in your models.
Note: To define a multi-columns relationship from a model A to another model B, both models must either extend FriendsOfHyperf\Compoships\Database\Eloquent\Model
or use the FriendsOfHyperf\Compoships\Compoships
trait
Syntax
... and now we can define a relationship from a model A to another model B by matching two or more columns (by passing an array of columns instead of a string).
We can use the same syntax to define the inverse of the relationship:
Example
As an example, let's pretend we have a task list with categories, managed by several teams of users where:
- a task belongs to a category
- a task is assigned to a team
- a team has many users
- a user belongs to one team
- a user is responsible for one category of tasks
The user responsible for a particular task is the user currently in charge for the category inside the team.
Again, same syntax to define the inverse of the relationship:
Contact
- Gmail
License
MIT
All versions of compoships with dependencies
hyperf/stringable Version ~3.1.0
hyperf/support Version ~3.1.0
hyperf/tappable Version ~3.1.0