atolson92

Пікірлер

@murtazahussainshaikh Ай бұрын

Thank you, professor. It was so helpful to understand the concept!

@Nāmarūpa1 8 ай бұрын

A is the Tax dept

@bobbastian760 9 ай бұрын

Ditch the intro. Yeah that really told me nothing.

@angstrom1058 Жыл бұрын

Entity A is the US government :) LOL

@summary017 Жыл бұрын

That's how our money goes to government banks in form of taxes .

@mohammadahmedragab837 Жыл бұрын

very well explained

@BeyondFrames777 Жыл бұрын

Speak something that normal humans understand.

@damandogra7386 11 ай бұрын

😂😂

@RaymondPeckIII Жыл бұрын

Wow, this is an impressively terrible explanation of how the rdbms would work. A table per customer? Are you kidding me? It's true that graph databases are optimized for following the arcs, and the query languages can express searches across multiple arcs much more naturally. That's why a graph database is a better mapping to this problem, not because you'd traverse multiple tables in an rdbms...

@bharathavamshikrishna9842 4 жыл бұрын

Simple and clear 👍

@kevinmccarthy7169 4 жыл бұрын

Thank you David!

@oliverbold9724 4 жыл бұрын

)*_*{

@condetvofficial6769 4 жыл бұрын

Hilo idol

@HIDlarissaTERRY 4 жыл бұрын

mY favourite!

@HIDlarissaTERRY 4 жыл бұрын

Lovely!

@bavishbalakrishnan4881 4 жыл бұрын

Awesome explanation ! Wanted to understand more on the subjective nature of Graph DBs over Relational ones.

@anitharahayu5278 4 жыл бұрын

Llll

@anitharahayu5278 4 жыл бұрын

Lllll

@anitharahayu5278 4 жыл бұрын

Lllll L

@anitharahayu5278 4 жыл бұрын

Lllll Lll

@ricardo_resende 5 жыл бұрын

OMG! So simple and precise... Thank you for sharing your knowledge

@piusranjan 5 жыл бұрын

Awesome

@cadmas9696 5 жыл бұрын

nice and simple. graph dbs can be daunting with various complexities

@benphua 6 жыл бұрын

Thank you that was useful

@benogidan 6 жыл бұрын

Good example and engaging

@DraganAlves 7 жыл бұрын

Brilliant

@MrSoso7676 8 жыл бұрын

I am pretty new at this so my question may be dubbed as .. stupid? But will ask anyway :) So does this imply that we would have a single node representing an entity as opposed to having a single table storing multiple entities? Follow up: In the event that we are storing information about 15000 entities, would we have 15000 nodes interconnecting? As opposed to a single table with 15000 entries?

@MajorCB211 6 жыл бұрын

a node has a type and can have multiple properties, so for example, a footballer will have an age, height, team. you can view all these properties when clicking on the node and you can view group of nodes by either their type or relationship. little bit late :)

@godnyx117 2 жыл бұрын

@@MajorCB211 Than you! Maybe a little bit late for OP and probably already figured out from his part but it helped me!