Tree: 3aa286f7c9

master

1.0.0

1.0.1

1.0.2

1.1.0

1.1.1

1.1.2

1.1.3

1.2.0

1.3.0

1.3.1

1.3.2

1.4.0

1.4.1

1.5.0

1.5.1

1.5.2

1.6.0

1.7.0

1.7.1

1.7.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '3aa286f7c9'

${ noResults }

Commit Graph

21 Commits (3aa286f7c9f8399b3d4ba93c502878925f1be7d5)

Author	SHA1	Message	Date
Alban Jubert	3aa286f7c9	Prepare v2.0.0 release	4 years ago
Alban Jubert	1afd088dbf	Added unit tests for issue #23	6 years ago
leandrogehlen	5c2ddca0cf	Cleanup	6 years ago
leandrogehlen	d2474cd1bd	Added tests	6 years ago
Leandro Gehlen	cd14cbcd04	Fixes error on update `hasMany` relation with composite key (#36) ... Fixes error on update `hasMany` relation with composite key	6 years ago
Alban Jubert	9f657bdb50	Fix a regression in Has One saving introduced by #33 fix.	6 years ago
Alban Jubert	e6807c7fb1	Fix for issue #33 ... Added the ability to set a relation scenario at runtime using the setRelationScenario method Added related tests	6 years ago
Alban Jubert	c76e4cf367	- Bug fix for has One relation ... - Bug fix for SaveRelationTrait	6 years ago
Alban Jubert	08f3ff8bd1	Added ability to delete related record after owner model delete	7 years ago
Alban Jubert	b74af4153d	Better support for hasOne relations saving (#22 and #23)	7 years ago
Alban Jubert	f1aea75953	Preparation of version 1.3.2	7 years ago
Alban Jubert	a34b436548	Fix for issue #22: when a has one relation is involved and the related models are linked using there primary key, the owner attribute should not be updated in order to pass the validation ... Added test cases for #22 issue	7 years ago
Alban Jubert	94a441c974	Implementation of enhancement #15: Allow saving extra columns to junction table	7 years ago
Alban Jubert	96c153f110	* Small refactoring. ... * Changed the way exceptions are thrown and handled during afterSave event (add error to relation attribute of the owner model, forced rollback if relevant)	7 years ago
Alban Jubert	4e0ec16f6d	Enh #3: Added the abilty to specify the validation scenario for related records ... Exception is now thrown (with a transaction rollback when relevant) in case a related record could not be saved during afterSave event	7 years ago
Alban Jubert	30377e1054	Preparing for enhancements #3, #5 and #15 to be able to set per relation properties	7 years ago
Alban Jubert	49cae2c76b	Fix for issue #12	8 years ago
Alban Jubert	797849e6a3	Add missing ProjectNoTransactions model test class	8 years ago
Alban Jubert	b917ed195f	Fix #1 issue: Setting null for a named relation is correctly handled now	9 years ago
Alban Jubert	dcc11984cd	Initial commit	9 years ago