Thank you, your explanation save my day, I was very confused at beginning and I watched this lesson and debug many times until got the trick how it works under the hood.
Thank you so much!!! Was able to get the point of Polymorphic right of the bat. Definitely worth it. Hoping I could take your course but it seems its too expensive for me at the moment.
Thanks, I have one question how will we reserve it means Photo::get() and It should fetch relationship data from relevant table example post or product.
Nicely explained. So if we have 3 tables like posts, products and images then we can make polymorphic relationship to bring data in optimized way. This can be done if we create two photo tables one is for post_photos and another is product_photos but for polymorphic relation we can reduce one table here. Thanks.
But if my Models should have only one photo per record, having regular BelongsTo would be totally enough. Am I right? Posts ---id ---text ---image_id Users ---id ---name ---image_id Images ---id ---filename Or there are still advantages to use Polymorphic Relations in this case?
If you have only those models strictly, then yes, your structure is good. But if in the future you're planning to have, for example, Comments with image_id or something else with image_id, polymorphic structure would allow you to achieve those new fields without changing any structure of DB cause you would reuse the same images database table.
i was confused on this i am doing it in rails its different code wise but im assuming its the same concept thank you for the video and for the excellent explanation
how to update? i have Polymorphic tags, and i can store success but i cant update fine, the result contact the tags,for example #hello #word and i add , #one.. the result in my input is #hello #word #one #hello #word #one my code.. $tags_name = explode(' , ' , $request->tags_name);
foreach($tags_name as $tag_name) { $post->tags()->attach(Tag::updateOrCreate(['name'=>$tag_name])); }
What is the error that you're getting? Maybe you shouldn't to ->attach() but instead create things manually, like PostTag::create('taggable_id' => $post_id) ... etc? (not sure what your polymorphic model is called, assumg PostTag)
Hi, thx for the answer, My problem is that I don't think I'm using the most optimal solution to update the registry, since I'm removing the tags with dettach and then adding them again ... es.stackoverflow.com/questions/418957/como-hacer-un-update-en-una-tabla-polimorfica,
i was able to get the concept behind polymorphism at the 1st 3 minutes of your explanation Povilas! you teach very well!
Great explanation as always. You're the go-to channel for anything laravel-related.
Thank you, your explanation save my day, I was very confused at beginning and I watched this lesson and debug many times until got the trick how it works under the hood.
Thanks for sharing. I now understand perfectly how to use polymorphic relationships.
Thank you so much!!! Was able to get the point of Polymorphic right of the bat.
Definitely worth it. Hoping I could take your course but it seems its too expensive for me at the moment.
thank you for your time. learned after 3 years. you are awesome
This is by far the best explanation I have seen! Thank you!
Thank you so much, i had this kind of issue,but wasn't aware that these relationships actually exist, you've explained it very well.
I wish real life relationships were this simple. :D Lit tutorial.
Thanks, Now I understand this topic.
Thank you sho much.
Best explanation I found. Thanks a mill
Thanks, I have one question how will we reserve it means Photo::get() and It should fetch relationship data from relevant table example post or product.
Great video, thanks.
As always - great explanation with examples. Thank you
Thanks! Love the example. Makes the concept very easy to understand
Really well explained, thank you very much for this!
How do we retrieve all data with relations.
Nicely explained.
So if we have 3 tables like posts, products and images then we can make polymorphic relationship to bring data in optimized way. This can be done if we create two photo tables one is for post_photos and another is product_photos but for polymorphic relation we can reduce one table here.
Thanks.
well said brother!
But if my Models should have only one photo per record, having regular BelongsTo would be totally enough. Am I right?
Posts
---id
---text
---image_id
Users
---id
---name
---image_id
Images
---id
---filename
Or there are still advantages to use Polymorphic Relations in this case?
If you have only those models strictly, then yes, your structure is good. But if in the future you're planning to have, for example, Comments with image_id or something else with image_id, polymorphic structure would allow you to achieve those new fields without changing any structure of DB cause you would reuse the same images database table.
i was confused on this i am doing it in rails its different code wise but im assuming its the same concept thank you for the video and for the excellent explanation
Great example, thanks!
how to update? i have Polymorphic tags, and i can store success but i cant update fine, the result contact the tags,for example
#hello #word
and i add , #one.. the result in my input is
#hello #word #one #hello #word #one
my code..
$tags_name = explode(' , ' , $request->tags_name);
foreach($tags_name as $tag_name)
{
$post->tags()->attach(Tag::updateOrCreate(['name'=>$tag_name]));
}
What is the error that you're getting?
Maybe you shouldn't to ->attach() but instead create things manually, like PostTag::create('taggable_id' => $post_id) ... etc? (not sure what your polymorphic model is called, assumg PostTag)
Hi, thx for the answer,
My problem is that I don't think I'm using the most optimal solution to update the registry, since I'm removing the tags with dettach and then adding them again ... es.stackoverflow.com/questions/418957/como-hacer-un-update-en-una-tabla-polimorfica,
@@nahueljj I think it's fine.
very clear explication, thanks
Hello from 2024. Still great video
Great video.
That mechanical keyboard sound, satisfying.
well explained...bravo
Thank you for your useful video.
Awesome🥰
thank you
Awesome!! Thank you very much
Thanks very much, but this video not include Factories and Seeders
amazing
cool. 👍 i just can't bring myself to liking this aproach. one-too-many sleepless nights with slow db without keys. :) but it might have it's uses.
Thank you :)
Excellent video… you just saved my butt! Do you have any Udemy courses?
Thanks Mike. Not on udemy, but on teachable - see laraveldaily.teachable.com
!!!!!
Thank you very match !
You are the best teacher !
From russia. putin-juilo
AAAARGH SO BRIGHT! x_x
Got it
Great explanation From 2024
best
thank you, very informative!