MySQL 9 - Many-to-Many Relationship

~~~~~~~~~~~~~~~ CONNECT ~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~ SUPPORT ME ~~~~~~~~~~~~~~

🅑 Bitcoin - 3HnF1SWTzo1dCU7RwFLhgk7SYiVfV37Pbq
🅔 Eth - 0x350139af84b60d075a3a0379716040b63f6D3853

[vandolphreyes]

Completed the 3 tutorials about relationship. Simple and clear explanation, no question at all. Thanks mate!

[bigollie]

You're a fucking GEE bro. Thank you so much. I was struggling with the concept, now its clear. I love that you're still rocking the chalkboard. Keep up the good work

[xIvalicex]

The moment he split those two tables I knew I needed to keep learning from this guy...

[TuongVan-gi]

3:09 we have duplicated data in `title` and in 4:55 we also have duplicated data (9, 1) (8, 1)
So why does it acceptable for duplicating data in a junction table?

[StevenSenjaya]

Crisp and clear explanation. Thank you, sir!

[GrumpyOldMan]

Complicated example. Why not something like a table of papers, with some having more than one author, and a table of authors, with some having (co)authored more than one paper?

[JersonLaroya]

Thank you, you really helped me. Our prof just told us to break many to many relationship without explaining why and how.

[MarkEdwardTan]

I thought it was called Pivot tables. Thanks for clearing that up to me - Intermediary tables is the term I'm looking for.

[odysseasfilippidis]

I think there is another solution to this: putting the listing id in the users table. This way you'll have one foreign key in each table. I think this is called bidirectional relationship, whereas the one you're showing is the unidirectional. Correct me if I'm wrong. (great explanation by the way)

[bhagyashingale]

I would store the keys of the other tables in an array column. Then fetch them from the other table as and when required. This should work for most use cases unless the size of the array is going to be too large i.e 100, 000's of id's

[Jellonova]

Does anyone know if Caleb has a hands on sql programming playlist using these concepts like many to many relationships?

[dkg]

Thanks a lot man, was badly looking for this solution

[faxxaznone]

hi caleb, i'm wondering where is your old playlist about PHP and MYSQL ? i wanted to rewatch it also but i couldn't find those playlist anymore.

[tomoriger]

So I have a question...

Let's say you wanted to keep track of apartments that sold in neighborhoods A, B, and C. There was no easy way of getting their address to make them unique, but you did know if they were a studio, 1 bedroom, etc. You also know the price and month they sold for.

How would you organize the data when there seems to be no way to make anything unique to create a primary key? For example, there may be several 2 bedrooms that sold for the same price in the same month and in 2 of the 3 neighborhoods.

[Kwisatsoundman]

The way you split out your two preexisting tables thanks to your sword-chalk is kind of hard (Given the pain that these tables must have felt), but I understand it's for the cause, so I forgive you.

[kabulenglish]

you teach and explain pretty good Caleb. thanks

[aldehc]

You're the Thanks a lot, in my native language I couldn't find much information about breaking it down... Now I know.

[PHPRunnerTipsAndTricks]

Hi Caleb, thanks for your excellent explanation. I did not have any issues with many to many, as I understand this for many years already. Can tell me if you consider a one to one relationship useful, and if you do, please explain why. Thanks in advance.

[Khatastrov]

Pretty clear and well explained. Thank you !

[DanielCatalaa]

I have been wanting to setup tables that relate as many-to-many for a long time. Thank you for your tutorial! Actually many many thanks :o)