Database Design 15 - Designing One-to-One Relationships

Подписаться 627 тыс.

Просмотров 37 тыс.

50% 1

Start your software dev career - calcur.tech/dev-fundamentals 💯 FREE Courses (100+ hours) - calcur.tech/all-in-ones
🐍 Python Course - calcur.tech/python-courses
✅ Data Structures & Algorithms - calcur.tech/dsa-youtube
~~~~~~~~~~~~~~~ CONNECT ~~~~~~~~~~~~~~~
✉️ Newsletter - calcur.tech/newsletter
📸 Instagram - / calebcurry
🐦 Twitter - / calebcurry
🔗 LinkedIn - / calebcurry
▶️ Subscribe - calcur.tech/subscribe
👨🏻‍🎓 Courses - www.codebreakthrough.com
~~~~~~~~~~~~~~ SUPPORT ME ~~~~~~~~~~~~~~
↪ My Amazon Store - www.amazon.com/shop/calebcurry
🅿 Patreon - calcur.tech/patreon-calebcurry
🅖 GitHub Sponsors - github.com/sponsors/CalebCurry
Ⓟ Paypal - paypal.me/calcur
🅑 Bitcoin - 3HnF1SWTzo1dCU7RwFLhgk7SYiVfV37Pbq
🅔 Eth - 0x350139af84b60d075a3a0379716040b63f6D3853
📈 Buy Bitcoin - calcur.tech/crypto
Reserve the Ruby Steel crypto rewards card and get a $25 bonus (use affiliate code "Caleb") - calcur.tech/crypto

Наука

Опубликовано:

22 июл 2014

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 22

@Millarayr 7 лет назад

Excellent explanation! You were able to make me understand something that my teacher couldn't. Thank you very much :)

@robertbrozewicz8003 8 лет назад

I start to understand the concepts much better now and the reason why we have databases at all,. It is an organized collection of data with clearly defined relationships between entities. Each entity has an attribute or more that is an intrinsic part of it and either serves to describe itself or is necessary for interaction with other related entities. We need to internalize concepts and ideas so well that designing a database will become a natural thing. Also the coding part of that, when we decide to use SQL, MySql or maybe some own little database based on native code even. I have subscribed and enjoy the series.,

@kevingarner7231 9 лет назад

Yep, subscribed Thanks Caleb

@codebreakthrough 10 лет назад

Watch this video to learn about designing One-to-One Relationships. Please comment and click like! buff.ly/1tL4lHL

@Alex-ui5uu 4 года назад

This is the explanation that I needed. Thank you!!

@edvardtheorangeelephant5077 10 лет назад

Now, a serious comment. I've been learning the concept of proper table format just from messing around in Open Office Calc, trying to make some random character generators for RPG purposes. CLARITY IS IMPORTANT. ^^

@juliovasquez3039 7 лет назад

Thank you!

@no-qm1kn Год назад

better than uni courses

@edvardtheorangeelephant5077 10 лет назад

I love the way your pronounce attribute. ;P a-Tribute instead of A-tri-Bute. Suddenly I'm thinking of "giving a Tribute!" to Caesar. xD

@tzezc 8 лет назад

thanks a lot

@zvit 8 лет назад

Hey Caleb, great series! (subscribed). I have a question about design. You mentioned in this video at the very end, how if you have 2 people in a relationship on a dating website, you can just have a "relationship" field that would contain another user's ID. However, in earlier videos you said (and I agree) that you will name both sides of a key the same - for good design. So in order to implement this in the dating site example, you would need a new table with two fields - relation1 and relation2 where both would be called "used_id". Otherwise, you can't give the same key name or else you would have two fields called "user_id" in the entity. Yes, of course one would be a primary and one not but for "good design" sake, wouldn't this be confusing?

@you92770 7 лет назад

thank you

@richard2845 6 лет назад

Thanks

@vipinkoul9129 6 лет назад

You are awesome, kid! Gifted child :)

@borisrunakov1662 2 года назад

If the credit card has a reference to the user and the user to a credit card ID, what entity and how do you create first?

@alexisrs127 9 лет назад

In the implementation of Person and CreditCard in which just 1 person can have a credit card an vice versa. the FKcard# in Person is from table CreditCard. Question: how the table CreditCard is related to Person. This seems to be as one to many, what is the difference becuse in 1 to 1 and 1to many share FK from the other table