Thanks, this is great ;) My Proffesor linked this video in an exercise and it's actually really helpful and interesting. Best 20 minutes on leecture I have spend today
Very well explained Phillip. I appreciate you took time and created this video. All the best with whatever you are doing and I will be happy to return favor with some way in future. Thanks again. Cheers.
hi Philip, Thank you (a lot) for this easy to understand video. You mentioned a flat table approach in the explanation, to be discussed in a later video. Did you make this video, and if so, do you have the URL?
Wow. I've intuit something similar before(without knowing EAV was the official name/concept of it! ). I used MSSQL Variant type and have one value table for all types. But eventually the junior devs and my boss eventually didnt like it because it was too rich for their blood. Wusses!!! I used it to build own dynamic survey data collector. Where i dynamically build questionnaire on the fly(like my very own SurveyMonkey). I explained and justified the design to them like a million times but they just dismiss it as being too complex. They were also afraid of my dynamic SQL pivoting to generate the flat table. It worked perfectly!!!
Good explanation, you have mentioned that Magento moved further with "flattening" all tabes together so it will be easier to write a query, so are you going to create video for it? Thank you.
considering the high frequency of change for data like inventory there is a possibility of a read write conflict. for attributes, any number of designs would probably be better or more modern. document storage is preferable to rdbms for modern applications but at some point you will need a ledger, so you'll be joining to tables that have schemaless or json types. again, depending on your application, this could lead to unexpected read write.
@@philwinkle hi, thanks for answering. which document storage support geo search and full text search. Thanks Ah i just discover postgres support jsonb is like document storage
Good video, except at the end you're just plain wrong. type_id is directly linked to you label (thus attribute_id) so you don;t need to store it in the datetime and varchar table.
"That's for another episode" ... but there's no other episodes. Sad times.
Why I don't see to much "teachers" using excel to explain DB like this guy? This is simply game-changing. Ty so much
Thanks, this is great ;) My Proffesor linked this video in an exercise and it's actually really helpful and interesting. Best 20 minutes on leecture I have spend today
I never left a comment on youtube before, but I want to say that this is a super great video! I hope you release more videos like these!
Very well explained Phillip. I appreciate you took time and created this video. All the best with whatever you are doing and I will be happy to return favor with some way in future. Thanks again. Cheers.
Great video. Very simple explanation of a very complex thing in DBMS. Thanks for making it..
Man. Nobody explained it the way you did. Good for you.
hi Philip, Thank you (a lot) for this easy to understand video. You mentioned a flat table approach in the explanation, to be discussed in a later video. Did you make this video, and if so, do you have the URL?
I'd like to see more about the flat table approach if you ever get time. This was an excellent video!
Wow. I've intuit something similar before(without knowing EAV was the official name/concept of it! ). I used MSSQL Variant type and have one value table for all types. But eventually the junior devs and my boss eventually didnt like it because it was too rich for their blood. Wusses!!! I used it to build own dynamic survey data collector. Where i dynamically build questionnaire on the fly(like my very own SurveyMonkey). I explained and justified the design to them like a million times but they just dismiss it as being too complex. They were also afraid of my dynamic SQL pivoting to generate the flat table. It worked perfectly!!!
Same stroy here mate
Very good and informative video please keep your good work up
This is one of the best videos explaining EAV...Thanks!
Thank you Philip it couldn't be a better explanation.
Thanks for this simple explanation,
I think column `type_id` in `Attribute` table is not necessary as we already put it in `Value` table
Thanks for this great video. Even foreigners like me with another native language could understand you! Great explanation!
Hi @Phillip, Thanks for a clear explanation regarding EAV , Im currently working on a warehouse inventory and I may use this approach to products :).
Good explanation, you have mentioned that Magento moved further with "flattening" all tabes together so it will be easier to write a query, so are you going to create video for it?
Thank you.
great example.... definitely improved my understanding in EAV.... from zero to hero now
very nice , really appreciate the way you demystified it.
Perfect explanation!
I like you video thanks man.... I've been searching for the FLAT TABLE you promise man where can I find it?
Excellent ! Highly Appreciated.
Super duper explanation, thanks a lot, upload more bro
What about flat table? can anyone share any link to understand how to fetch data?
Thank you you have clear my concept about eav
Excellent 👌 Upload more videos. You can Rock the Magento
Thank u very much. The last thing about entity ID is what I need
Meant a lot, this video. Thanks Philip.
How can I integrate date range with thia or other data types that has range?
And when is the next episode??? 🤔️
thank you Phillips, it's supper clear
Good and easy to understand. Very helpful, thanks a lot!
This is awesome!
Slimply Excellent 👍🙏
Hello! Thanks for video. But can u explain, what query i have to use to get all attributes of some entity? Just a lot of joins?
So downside of this method is performance issues. But we can overcome performance issues by creating indexes right?
Great video! Thanks for that.
how about the group_id? is it still on customer table?
This video was very helpful.
Please do more videos on Magento 2 extension development
Great Video.
Can we use ltree in postgres to do product variation and stock. Is it better or not for this purpose. Thanks
considering the high frequency of change for data like inventory there is a possibility of a read write conflict. for attributes, any number of designs would probably be better or more modern. document storage is preferable to rdbms for modern applications but at some point you will need a ledger, so you'll be joining to tables that have schemaless or json types. again, depending on your application, this could lead to unexpected read write.
@@philwinkle hi, thanks for answering. which document storage support geo search and full text search. Thanks
Ah i just discover postgres support jsonb is like document storage
Thank You Phillip
Hey thanks for this video Please release next video. Waiting for it :)
Superb
Thanks so much
Thank you :)
thanks!
Good video, except at the end you're just plain wrong. type_id is directly linked to you label (thus attribute_id) so you don;t need to store it in the datetime and varchar table.
thanks a lot ... :)
My University linked this Video to do an worksheet about EAV XDD
That's cool! 👊
@@philwinkle is there any chance you'll post the next episode??
uni ulm std war hier