This means that, Eloquent will look for the value of the user's id column in the user_id column of the Phone record. In addition, Eloquent assumes that the foreign key has a value matching the id (or the custom $primaryKey) column of the parent. If we wish to override this convention, we may pass a second argument to the hasOne method: return $this->hasOne('App\Phone', 'foreign_key') In cases as this, the Phone model will be automatically assumed to have a user_id foreign key. The Eloquent determines the foreign key of the relationship based on the model name.
Dynamic properties will allow us to access relationship methods as if they were properties defined on the model: $phone = User::find(1)->phone Once the relationship has been defined, we can then retrieve the related record using Eloquent's dynamic properties. The first argument that is passed to the hasOne method is the name of the related model. Then the phone method should call the hasOne method and return its result: hasOne('App\Phone') For us to define this relationship, we have to place a phone method on the User model. For instance, a User model may be associated with one Phone. The one-to-one relationship is a very basic relation.
#LARAVEL ELOQUENT HOW TO#
For instance, we may chain additional constraints on this posts relationship: $user->posts()->where('active', 1)->get() īefore we dive too deep into using relationship, let us learn how to define each type.
Just like Eloquent models themselves, Eloquent relationships also serve as powerful query builders, and defining relationships as methods provides powerful method chaining and querying capabilities. We define eloquent relationships as methods on our Eloquent model classes. Eloquent make the management of relationships in our application very easy. For instance, a blog post may have many views and reacts, an order can be related to the customer who placed t. In an application there is often a relationship between the database tables.
0 kommentar(er)
