MySQL Workbench Design Walkthrough

A walk through on how to design databases in MySQL Workbench.

[geerliglecluse]

One of the best MySql videos I've come across, and certainly the most practical one!

[carlblaskowitz]

10:16 Happy child just got a home cooked meal... Bonus points achieved!
This tutorial blows away all the others, thank you.

[marioibarra]

Thanks. Great tutorial. I have difficulty understanding the workbench. You make it easy. A little bit fast for beginners, but very well explained.

[andrewkamoha]

16:56 "It gives you an opportunity to review the SQL that it's going to use to create those things."
Amazing !!! My 'AHA Moment' of the day !!!! +1

[steventhehistorian]

14:45 "People_Sex is a VARCHAR 1... It's a choice of one or the other... This seems like an obvious example..."

lol Nov 3, 2016 was a simpler time.

[mariuspet]

Amazing, please do more videos(crash courses) you are very good at explaining.

[TommyJustTommy]

Hi,
Great tutorial, but I have several questions:
1) Why did you implement 1-to-many relation between people and company by company_has_people table? Why not add a foreign key to the "people" table? Same for addresses, why not to add a foreign key to the "companies" and "people"? Is it some sort of normalization? Maybe something like keeping the coupling low? What possible benefits can it bring?
2) Why do you need a separate primary key in "companies_have_people"? As the relationship is identifying, the foreign keys are primary keys as well and they form a complex primary key, that is the combination of "people_id" and "companies_id" works as a two element primary key. Could you explain the reason of the separate primary key("company_has_people_id")?
3) Why did you leave Not Null constraints == false?
To my opinion, prefixes, like "people_" are not necessary here, we use aliases or full table names in queries, so a query would look like SELECT some_fields FROM people p JOIN ... something WHERE p.people_first = "John". We already have that "people_" in the form of "p." or even "people.", if you don't like aliases. Such prefixes also mess the autocompletion tips up: like when you need some field, you write "p.people_..." and you have the complete list of all the fields, which slows your work.
Thank you

[andrewderevianko]

For a long time I was looking for something similar. There are no similar lessons in the Ukrainian youtube space. Thank you for lesson.

[xXHelsingGamingXx]

Please do a full series on MYSQL series with MY SQL work bench with mac and windows as well.

[hilllasten]

This video is really helpful. Thank a lot.

[JameyNewly]

Cant thank you enough! Your video series have been really helpful!

[anmolsingh]

Yes this youtube recommendation is best you tube really care about me

[wpunique]

Great tutorial, really helpful thanks!

[_m.a-x]

At 7:00 how did you achieve many-to-many relationship by using 1:1 connectors? If I do not create a middle table and just throw in the n:m relationship between company and people, the middle table will auto-create with FK auto-populated, but the relationship to the table will be 1:m from both tables. What is the difference?
Also, you created the 3rd PK in the middle table. If I were not to create it and leave the 2 FK as primary for this table, would I achieve then the restriction that 1 company cannot have the same employee listed 2 times?
Thank you very much! Great video!

[phuongla]

This is awesome. But I do have a question: How do we go back and view the ER-Diagram after we have used to generate (Forward Engineer) our database?

[bennywon]

Thank you very much for the video, like and subscribed.

[adriansegura]

thank you for uploading this helpful video

[wabafethacker]

Im having an issue I hope u can help with i tried to set the items to cascade and it crashed the software on linux and win with a hand created schema and reverse engineered schema from mysql via workbench

[ArtIsDrawing]

when I change datatype it gives me an error and I cant change datatype :/