Tree: a34b436548

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 'a34b436548'

${ noResults }

Commit Graph

8 Commits (a34b436548e30538275d4502fe177d6b22fe2805)

Author	SHA1	Message	Date
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	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	8 years ago
Alban Jubert	49cae2c76b	Fix for issue #12	8 years ago
Alban Jubert	797849e6a3	Add missing ProjectNoTransactions model test class	9 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