- Fix #45: Newly created Has One relations were not deleted in case owner model validation failed (thx @douglasgsouza)
- Fix #23: Relational data was not loaded for nested relational models (thx @toreonify)
- Enh #42: Add the ability to retrieve old relations values
- Enh #43: Add the ability to retrieve and mark dirty relations
- Bug #36: Fix an issue with HasMany relations with composite keys (thx @leandrogehlen)
- Bug #41: Fixes error loading
hasMany
relation without referenced key in data (thx @leandrogehlen) - Fix for transaction being started during the
beforeValidate
event (thx @leandrogehlen)
- Enh #37: Add a
relationKeyName
property to determine the key used to load relations data.
- Removed
isModelTransactional
protected method. Transactions are not started by the behavior any more.
- Fix a regression in Has One saving introduced by #30 fix.
- Bug #33: Custom relation scenario was set too late and was preventing attributes from being correctly set (thx @phrakon)
- New method
setRelationScenario
can set a relation scenario at runtime
- Light refactoring
- Updated documentation
- Enh #5: Ability to automatically delete related records along with the main model
- Bug #30: HasOne relation saving issue (thx @phrakon)
- Fix for SaveRelationTrait (thx @leandrogehlen)
- Some code refactoring
- Yii2 requirements raised to 2.0.14
- Bug #24: Fix a regression introduced in 1.4.0 release where validation of hasOne relations was not triggered. (thx @dabkhazi)
- Bug #25: Fix for Yii 2.0.14 compatibility. Has many relations were not saved. (thx @SanChes-tanker)
- Enh #15: Allow to save extra columns to junction table (thx @sspat)
- Bug #22: Fix for HasOne relation pointing to the owner primary key (thx @mythicallage)
- Enh #19: Support for defining relations through the
getRelation
method (thx @execut) - Enh #21: Better support of partial composite keys (thx @execut)
- Enh #3: Ability to define validation scenario for related records
- Enh #7: Exception logging during
beforeValidate
andafterSave
events. - More test cases
- False positive
testLoadRelationsShouldSucceed
test case
- afterSave throw exception if a related record fail to be saved. In that case, a database rollback is triggered (when relevant) and an error is attached to the according relation attribute
- related record are now correctly updated based on there primary key (Thanks to @DD174)
- Use of
ActiveQueryInterface
andBaseActiveRecord
to ensure broader DB driver compatibility (Thx @bookin)
- Bug #13: Relations as array were inserted then deleted instead of being updated
- Fix for empty value assignment on HasMany relations
- Bug #12: Nesting level too deep – recursive dependency error during object comparing (Thx @magicaner)
- SaveRelationsTrait to load related data using the
load()
method - ability to set HasMany relation using a single object (Thanks to @sankam-nikolya and @k0R73z))
- Fix a bug that was preventing new records to be correctly saved for hasMany relations.
- Setting null for a named relation is now correctly handled.
- A new related model instance was previously generated instead.
Initial release