Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/voskobovich/yii2-many-to-many-behavior
This behavior soon will be DEPRECATED. See the link:
https://github.com/voskobovich/yii2-many-to-many-behavior
Last synced: 5 days ago
JSON representation
This behavior soon will be DEPRECATED. See the link:
- Host: GitHub
- URL: https://github.com/voskobovich/yii2-many-to-many-behavior
- Owner: voskobovich
- License: other
- Created: 2014-12-07T15:02:43.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2016-12-01T14:45:10.000Z (about 8 years ago)
- Last Synced: 2024-05-18T17:45:02.631Z (9 months ago)
- Language: PHP
- Homepage: https://github.com/voskobovich/yii2-linker-behavior
- Size: 94.7 KB
- Stars: 113
- Watchers: 13
- Forks: 31
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
Yii2 ManyToMany Behavior
========================
This behavior soon will be **DEPRECATED**.
See the new version [**Yii2 Linker Behavior**](https://github.com/voskobovich/yii2-linker-behavior).
## About
This behavior makes it easy to maintain many-to-many and one-to-many relations in your ActiveRecord models.
[](https://packagist.org/packages/voskobovich/yii2-many-many-behavior)
[](https://packagist.org/packages/voskobovich/yii2-many-many-behavior)
[](https://packagist.org/packages/voskobovich/yii2-many-many-behavior)
[](https://packagist.org/packages/voskobovich/yii2-many-many-behavior)
[](https://travis-ci.org/voskobovich/yii2-many-to-many-behavior)
Support
---
[GutHub issues](https://github.com/voskobovich/yii2-many-to-many-behavior/issues).
Usage
-----
1. In your model, add the behavior and configure it
2. In your model, add validation rules for the attributes created by the behavior
3. In your view, create form fields for the attributes
Adding and configuring the behavior
-----------------------------------
As an example, let's assume you are dealing with entities like `Book`, `Author` and `Review`. The `Book` model has the following relationships:
```php
public function getAuthors()
{
return $this->hasMany(Author::className(), ['id' => 'author_id'])
->viaTable('book_has_author', ['book_id' => 'id']);
}
public function getReviews()
{
return $this->hasMany(Review::className(), ['id' => 'review_id']);
}
```
In the same model, the behaviour can be configured like so:
```php
public function behaviors()
{
return [
[
'class' => \voskobovich\behaviors\ManyToManyBehavior::className(),
'relations' => [
'author_ids' => 'authors',
'review_ids' => 'reviews',
],
],
];
}
```
Relation names don't need to end in `_ids`, and you can use any name for a relation. It is recommended to use meaningful names, though.
Adding validation rules
-------------------------
The attributes are created automatically. However, you must supply a validation rule for them (usually a `safe` validator):
```php
public function rules()
{
return [
[['author_ids', 'review_ids'], 'each', 'rule' => ['integer']]
];
}
```
Creating form fields
--------------------
By default, the behavior will accept data from a multiselect field:
```php
= $form->field($model, 'author_ids')
->dropDownList($authorsAsArray, ['multiple' => true]) ?>
...
= $form->field($model, 'review_ids')
->dropDownList($reviewsAsArray, ['multiple' => true]) ?>
```
Known issues and limitations
----------------------------
* Composite primary keys are not supported.
* Junction table for many-to-many links is updated using the connection from the primary model.
* When using a function to calculate the default value, keep in mind that this function is called once, right before the relations are saved, and then its result is used to update all relevant rows using one query.
* Relations are saved using DAO (i. e. by manipulating the tables directly).
### Custom getters and setters ###
Attributes like `author_ids` and `review_ids` in the `Book` model are created automatically. By default, they are configured to accept data from a standard select input (see below). However, it is possible to use custom getter and setter functions, which may be useful for interaction with more complex frontend scripts. It is possible to define many alternative getters and setters for a given attribute:
```php
//...
'author_ids' => [
'authors',
'fields' => [
'json' => [
'get' => function($value) {
//from internal representation (array) to user type
return JSON::encode($value);
},
'set' => function($value) {
//from user type to internal representation (array)
return JSON::decode($value);
},
],
'string' => [
'get' => function($value) {
//from internal representation (array) to user type
return implode(',', $value);
},
'set' => function($value) {
//from user type to internal representation (array)
return explode(',', $value);
},
],
],
]
//...
```
Field name is concatenated to the attribute name with an underscore. In this example, accessing `$model->author_ids` will result in an array of IDs, `$model->author_ids_json` will return a JSON string and `$model->author_ids_string` will return a comma-separated string of IDs. Setters work similarly.
Getters and setters may be ommitted to fall back to default behavior (arrays of IDs).
###### NOTE ######
The setter function receives whatever data comes through the `$_REQUEST` and is expected to return the array of the related model IDs. The getter function receives the array of the related model IDs.
###### COMPATIBILITY NOTE ######
Specifying getters and setters for the primary attribute (`author_ids` in the above example) is still supported, but not recommended. Best practice is to use primary attribute to get and set values as array of IDs and create `fields` to use other getters and setters.
### Custom junction table values ###
For seting additional values in junction table (apart columns required for relation), you can use `viaTableValues`:
```php
...
'author_ids' => [
'authors',
'viaTableValues' => [
'status_key' => BookHasAuthor::STATUS_ACTIVE,
'created_at' => function() {
return new \yii\db\Expression('NOW()');
},
'is_main' => function($model, $relationName, $attributeName, $relatedPk) {
return array_search($relatedPk, $model->author_ids) === 0;
},
],
]
...
```
### Setting default values for orphaned models ###
When one-to-many relations are saved, old links are removed and new links are created. To remove an old link, the corresponding foreign-key column is set to a certain value. It is `NULL` by default, but can be configured differently. Note that your database must support your chosen default value, so if you are using `NULL` as a default value, the field must be nullable.
You can supply a constant value like so:
```php
...
'review_ids' => [
'reviews',
'default' => 17,
],
...
```
It is also possible to assign the default value to `NULL` explicitly, like so: `'default' => null`. Another option is to provide a function to calculate the default value:
```php
...
'review_ids' => [
'reviews',
'default' => function($model, $relationName, $attributeName) {
//default value calculation
//...
return $defaultValue;
},
],
...
```
The function accepts 3 parameters. In our example `$model` is the instance of the `Book` class (owner of the behavior), `$relationName` is `'reviews'` and `$attributeName` is `'review_ids'`.
If you need the db connection inside this function, it is recommended to obtain it from either the primary model (`Book`) or the secondary model (`Review`).
```php
function($model, $relationName, $attributeName) {
//get db connection from primary model (Book)
$connection = $model::getDb();
...
//OR get db connection from secondary model (Review)
$secondaryModelClass = $model->getRelation($relationName)->modelClass;
$connection = $secondaryModelClass::getDb();
...
//further value calculation logic (db query)
```
### Applying the behaviour several times to a single relationship ###
It is possible to use this behavior for a single relationship multiple times in a single model. This is not recommended, however.
### Using the behaviour with relations that are using the same junction table ###
When you are implementing multiple ManyToMany relations in the same model, and they are using same junction table,
you may face and issue when your junction records will not be saved properly.
This happens because old junction records are dropped each time new relation is saved.
To avoid deletion of records that were just saved, you will need to set `customDeleteCondition` param.
This delete condition will be merged with primary delete condition and may be used to fine tune your delete query.
For example, let's imagine that we develop a scientific database for botanical laboratory.
We have a model called "Sample" for different plants samples, model called "Attachment" for related files
(photos or documents) and junction table "sample_attachments".
And we want to divide all those files into separate fields in the "Sample" model (raw material pictures,
molecular structure, etc) by introducing field "type" in the junction table.
In such case, the resulting "Sample" model will look like this:
```php
public function behaviors()
{
return [
'manyToMany' => [
'class' => ManyToManyBehavior::className(),
'relations' => [
'rawMaterialPicturesList' => [
'rawMaterialPictures',
'viaTableValues' => [
'type_key' => 'RAW_MATERIAL_PICTURES',
],
'customDeleteCondition' => [
'type_key' => 'RAW_MATERIAL_PICTURES',
],
],
'molecularStructureList' => [
'molecularStructure',
'viaTableValues' => [
'type_key' => 'MOLECULAR_STRUCTURE',
],
'customDeleteCondition' => [
'type_key' => 'MOLECULAR_STRUCTURE',
],
],
],
],
];
}
public function getRawMaterialPictures()
{
return $this->hasMany(Attachment::className(), ['id' => 'related_id'])
->viaTable('sample_attachments', ['current_id' => 'id'], function ($query) {
$query->andWhere([
'type_key' => 'RAW_MATERIAL_PICTURES',
]);
return $query;
});
}
public function getMolecularStructure()
{
return $this->hasMany(Attachment::className(), ['id' => 'related_id'])
->viaTable('sample_attachments', ['current_id' => 'id'], function ($query) {
$query->andWhere([
'type_key' => 'MOLECULAR_STRUCTURE',
]);
return $query;
});
}
```
Installation
------------
The preferred way to install this extension is through [composer](http://getcomposer.org/download/).
Either run
```
php composer.phar require --prefer-dist voskobovich/yii2-many-many-behavior "^3.0"
```
or add
```
"voskobovich/yii2-many-many-behavior": "^3.0"
```
to the require section of your `composer.json` file.