Even though I read the documents over and over again, I can't understand this situation. I am researching but it is not possible to understand. Finally I found the solution to write here. When I examine the Laravel documents, I see the migration structure is the same. I also create and test with these migrations, but I can't understand the main difference. What is the difference?
One To One Polymorphic
posts id - integer name - string
users id - integer name - string
images id - integer url - string imageable_id - integer imageable_type - string
One To Many Polymorphic
posts id - integer title - string body - text
videos id - integer title - string url - string
comments id - integer body - text commentable_id - integer commentable_type - string
@beyondelayer To sum up:
A one-to-one polymorphic relationship allows a model to belong to one instance of another model across different types of models, resulting in a unique association for each parent model. In contrast, a one-to-many polymorphic relationship allows a model to belong to multiple instances of another model across different types of models, enabling a single model to associate with various parents of different types.
@tisuchi So, just for my Understanding with the One To One Example in the OP, there couldn't be 2 or more images connected to any post or user.. right?
An example might be:
one-to-one
User is associated with one phone number and one email
one-to-many
User is associated with 2 or more phone numbers and 2 or more email addresses.
But just example.
The table design of one to one and one to many could well be identical.
Its difficult to explain in words, but each of the "many" is no different to a single record in one to one.
The distinction in the naming really just helps eloquent understand that the relationship has one or could have many records on one side of the relationship
According to me there is no real difference between both relationships.
@snapey explains it very well ;).
Please or to participate in this conversation.