Skip to content

Releases: cycle/orm

v2.12.2

16 Dec 13:41
v2.12.2
38360e9

Choose a tag to compare

What's Changed

  • Fix columns mapping in BelongsToMorphedLoader by @roxblnfk in #542

Full Changelog: v2.12.1...v2.12.2

v2.12.1

16 Dec 10:19
935dafc

Choose a tag to compare

What's Changed

Full Changelog: v2.12.0...v2.12.1

v2.12.0

12 Dec 15:49
8ac5a6e

Choose a tag to compare

What's Changed

Full Changelog: v2.11.1...v2.12.0

v2.11.1

24 Nov 12:51
5b0992d

Choose a tag to compare

What's Changed

Full Changelog: v2.11.0...v2.11.1

v2.11.0

09 Sep 11:27
d712c79

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2.10.1...v2.11.0

2.11.0-RC1

04 May 14:33
78009d9

Choose a tag to compare

2.11.0-RC1 Pre-release
Pre-release

What's Changed

Added a new behavior.

The ORM now will ignore relations and uninitialized Entity properties. In this case, unset($entity->relation) will not change the relation when saving, and it will hydrate it if the relation is loaded in the query.

To restore the old behavior where the ORM tries to fill all uninitialized relations if the entity is created not through the ORM (using new), and also treats unset as unlinking relations, pass an Options object into ORM constructor with the field $ignoreUninitializedRelations = false.

Full Changelog: v2.10.1...2.11.0-RC1

v1.8.2

04 Apr 20:59
7a15050

Choose a tag to compare

What's Changed

  • minor fix for php8.1 compatibility by @wezztt in #514

New Contributors

Full Changelog: v1.8.1...v1.8.2

v2.10.1

31 Mar 19:42
0b65906

Choose a tag to compare

What's Changed

Full Changelog: v2.10.0...v2.10.1

v2.10.0

17 Mar 13:03
44eaeb0

Choose a tag to compare

What's Changed

Explanation:

Let's imagine a situation:

  • We loaded a User entity from the database.
  • We made some changes to the entity (changed some fields) but did not save it to the database.
  • We requested several Comment entoitites from the database with eager loading of their authors (who are User entities).
  • One of the authors of the loaded comments is the User from the first point.

Before version 2.10:

  • The User entity, whose fields we changed, resets to the state from the database.

After version 2.10:

  • The loaded data does not change.
  • Only relations that were not loaded before can be hydrated.

If you want to work with new data from the database, you should clear the heap (fully or partially).

Full Changelog: v2.9.3...v2.10.0

v2.10.0-RC1

02 Mar 22:17
44eaeb0

Choose a tag to compare

v2.10.0-RC1 Pre-release
Pre-release

What's Changed

  • Change behavior of EntityFactory by @roxblnfk in #509
    It doesn't overwrite entity fields now

Full Changelog: v2.9.3...v2.10.0-RC1