Releases: cycle/orm
Releases · cycle/orm
v2.15.0
v2.14.3
v2.14.2
v2.14.1
What was changed
Now, for BelongsToMorphed relations, you can legally manually specify the morph_type column (without morph_id). This won't work if the entity is not new and the relation was set to null in this EM transaction (in this case, all relation fields will be prioritized to null). #556
Why?
Cycle ORM allowed some flexibility for the programmer. The recent fix that reset related fields broke some existing project codebases. To fix this, the old behavior was restored and supported with tests.
Even though this behavior is backed by tests, we still recommend not doing it this way for best practice reasons.
Full Changelog: v2.14.0...v2.14.1
v2.14.0
v2.13.2
v2.13.1
v2.13.0
What's Changed
- Add
UnitOfWork::hasPendingChanges()method by @roxblnfk in #548 - Add
orderByto HasOne loader by @markinigor in #487 - Optimize relations resolving by @peldax in #491
- Fix
TEntitygenerics by @rincler in #524 - Resolve issue #523 by @hiscaler in #525
New Contributors
- @hiscaler made their first contribution in #525
- @rincler made their first contribution in #524
- @peldax made their first contribution in #491
- @markinigor made their first contribution in #487
Full Changelog: v2.12.3...v2.13.0