• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
When Does Entity Attributes Get Filled

So I've been thinking a lot about these discussions around ORM and building relationships between items. All of the extensions are great, but I feel like the Entity class in CI4 is capable of a LOT, and I've been playing around with it a bunch to try and collect/install parameters based on relationships.

See this code here:
PHP Code:
namespace App\Entities;


User extends Entity
    public function __construct(array $data null)

        $this->attributes['posts'] = $this->getPosts();

    public function getPosts()
        $model = new PostsModel();

        $posts $model

        $this->attributes['posts'] = $posts;

        return $posts;

Imagine two tables and two Entities, Users and Posts. All you need to know is Users has an ID and can have many posts.

I know that I can call $user->posts and get the array of posts at any time. What I'm trying to do is build my Entity in such a way that when I call $user->toArray(), $user->posts becomes the array of posts. 

I tried initially putting in like a render() function that updates it but then I have to call it BEFORE ->toArray() and seems clunky.

I tried extending the __construct() function to update it then ($this->attributes['posts'] = $this->getPosts()) but I get an error message saying that ['id'] doesn't exist yet. Which is weird, because as parent::__construct runs, it should be filling in the data for that item from the database (I know an item is there and I can collect it, and I can display all properties of the entity fine, there just seems to be some kind of timing issue with how I'm using __construct and ['id'] hasn't been set yet in the process).

So the question remains... what can I do, so that everytime I instantiate an Entity of this type, the Entity can run code that will take the id property (when does it finally get loaded in?), collect related items and store them as an already available property (array) so I can just call ->toArray() directly after?

I should also note that I am receiving the Entity instance as the return type of a corresponding model.

Entities aren’t filled via the constructor when returned as part of a database query result (this includes Models), but rather have each attribute set one at a time. See e.g.:

You could probably create your own magic getter for posts that would load it on-the-fly, but I’m not entirely sure of its interaction with toArray(). I use this kind of “lazy load” for my Relations Entity trait and it works very well - no extra loading of related items if you don’t need them.

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  

  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2020 MyBB Group.