This video is so good, it's officially labeled as "bad-ass", and is 3NF compliant.
@MrLanorian22 сағат бұрын
Show demais!!!!😆
@josefkaras751923 сағат бұрын
wouldnt the year and month also break atomicity rule of 1nf?
@zaferemrekilinc413823 сағат бұрын
you are amazing
@huthaifamuayyad3491Күн бұрын
Thanks!
@huthaifamuayyad3491Күн бұрын
Very nice explanation and delivery of thoughts. Looking forward to more videos like this, explaining basic but important software principles.
@nintishiaКүн бұрын
Thanks a ton. You made it all so simple and easy.
@FrankKritzmanКүн бұрын
Great video, thank you!
@maria-rv7fk3 күн бұрын
THANK YOU! You explain this in a way that is practical and easy to follow. I much prefer this method of learning (visually and with examples) to memorizing a bunch of formal definitions. I understand learning about theory is good, but to really GET it I think you need someone to explain concepts like you do.
@mikemixsosa42644 күн бұрын
Great Video!
@piotrlezanski51567 күн бұрын
Hi, why in the second table Locker_id is cannot be primary key? It identifies every row, there are no duplicates.
@decomplexify3 күн бұрын
To make Locker ID the primary key is to declare that each Locker can only ever have one reservation. It means once this single reservation is made, no one can reserve that particular Locker ever again (because doing so would be a primary key violation). Focus not on the rows that happen to be in the table right now, but rather on the rules we want to enforce for what rows are and aren't allowed in the table.
@schwifty37857 күн бұрын
Great video dude Lots of loves and prayers
@Chris-tq1jy9 күн бұрын
Funny how Chat GPT recommended this video.
@Salalkhan10 күн бұрын
can you please tell me the Font name you are using in the video? Will be thankful
@decomplexify9 күн бұрын
Kalam
@thomaspotterdotexe13 күн бұрын
The PM and the owner : "F it, we will deploy it in 5 hour, we'll think about it later"
@adiporsh14 күн бұрын
It is not mandatory to have a primary key in 1NF. Every row should be unique which can be enforced by a single or multiple columns using a candidate key .
@decomplexify14 күн бұрын
I think you've misunderstood what a "primary key" is. A primary key doesn't have to consist of just a single column. A primary key can consist of multiple columns: for example, ALTER TABLE Customer_Address ADD PRIMARY KEY (Customer_ID, Address_Sequence_Number). In SQL, the only way you can prevent duplicate rows in a table is by adding a primary key constraint or unique key constraint to the table.
@adiporsh14 күн бұрын
@@decomplexify @decomplexify Primary key is not mandatory in 1 NF. Candidate key should work based on the requirement. However, primary key is desirable... i should've been specific...
@usingThaForce15 күн бұрын
I see why the frost machine be broken😅😅
@user-tb8xm1cb3s17 күн бұрын
Thanks for putting your time and energy in putting together this amazingly effective tutorial.
@NattixOMG18 күн бұрын
SELECT c.compund_name, c.compund_id FROM compund c JOIN compund_element_detail ced USING compound_id --Or (ON c.compund_id = ced.compound_id) WHERE ced.element_symbol = 'H'
@NattixOMG18 күн бұрын
would this not work? This is what I came up with before the video showed its answer. I guess I don't understand why the 3rd table 'Element' needs to be joined. Trying to get better at thinking through this so any help is appreciated
@NattixOMG18 күн бұрын
It's probably because the question asks for "Hydrogen", should work on reading questions fully lol
@orenzeshani19 күн бұрын
Every time a military surprise attack succeeds, this is what happened
@anudeepk739020 күн бұрын
Problem? Create a new table
@anudeepk739020 күн бұрын
Informative
@barrysarthak699020 күн бұрын
Thank you man One of the best explanations ever
@ScaleScarborough-jq8zx20 күн бұрын
Lots of mediocre shops out there are threatened by such sensible standards. “Our software, our system is strong because I said so!”
@SixTough21 күн бұрын
2NF and 3NF strive to create more tables where inconsitencies can happen in between tables and in case of error good data is overwritten irretrievably
@SixTough21 күн бұрын
An update anomaly preserves data and without it an error would simply get a wrong value
@pietrogazzera573323 күн бұрын
Thank you a lot!
@pietrogazzera573323 күн бұрын
INSERT INTO comments a VERY WELL DONE;
@itsandyagain23 күн бұрын
Awesome content. I understand this topic much better now. I'm having difficulty understanding a scenario where a partial update might happen. Could you possibly elaborate on that please?
@decomplexify23 күн бұрын
Good question! If a table structure permits inconsistency, then the update that we're required to do is more subtle and involved than it would otherwise be, therefore we're more likely to make a mistake. We may in fact not even realize that such updates are necessary. I've seen the following sort of example many times in real life. We have a table that holds transactions relating to an insurance policy, like premium transactions and claim transactions. Each such transaction is for a particular policy, occurs on a particular date, is of a particular type and for a particular amount, etc. Let's say a policy has certain properties, and one of these properties is "Policy Country". The designer has decided to include Policy Country on the transaction table, and therefore the transaction table is not in 3NF. It may simply never occur to the designer that Policy Country might change, e.g. Policy Country might be entered on the policy as Spain initially, and then some weeks later it might be corrected to Italy. Since the process for writing out a transaction involves copying the Policy Country from a policy table and stamping it on the transaction being generated, what will naturally happen in this case is that the first few transactions will show a Policy Country of Spain, and subsequent transactions will show a Policy Country of Italy. This will probably come to light only when somebody tries to report transaction amounts broken down by country and gets odd results.
@dus10dnd24 күн бұрын
Normalization isn't always sunshine and roses. If we go all the to 5NF and we're managing sales transactions, you would lose information regarding the cost a customer paid at the time, like if you're running a sale, or you adjust pricing, since you would be referencing the current price. So, denormalization does have value, sometimes.
@decomplexify23 күн бұрын
I think you're talking about a transaction table whose attributes are along the lines of: TRANSACTION_ID, TRANSACTION_DATE, CUSTOMER_ID, PRODUCT_ID, NUMBER_OF_UNITS_BOUGHT, UNIT_PRICE_THAT_THE_CUSTOMER_PAID. It's important to understand, however, that this table actually IS in 5NF - it's not denormalized. This is because UNIT_PRICE_THAT_THE_CUSTOMER_PAID doesn't have a functional dependency on PRODUCT_ID. If on the other hand there was an attribute called CURRENT_UNIT_PRICE, this attribute would have a functional dependency on PRODUCT_ID. The table would in this case not be normalized.
@yangfantan224724 күн бұрын
beautiful explanation! very clear and elegant, cut to the point
@agnesrahayu850026 күн бұрын
Many Thanks, sangat membantu saya untuk mengerjakan tugas kuliah.. Sukses terus kak :)
@muhammadtahasarwar211026 күн бұрын
Very clearly, unambiguously explained that is pleasing to the mind and feels like soothing to soul even when it is a pure technical topic rather than literature ❤
@zobzn127 күн бұрын
I don't get the example for the 4NF at all. Why do we need to add 2 rows, where is the rule wich says to do this way? Is this an artificial example? In real life green color just for one style is normal thing. I'm frustrated, why can't I comprehend it. Well, I also didn’t understand the fifth form even more. Even the problem itself, not to mention the solution.
@lilianchauvel369428 күн бұрын
What a boss, trully simple to understand, thx a lot
@doniaelfouly4142Ай бұрын
thanks
@zelousfoxtrot3390Ай бұрын
Well that was two weeks of lectures summed up nicely. THANK YOU!
@anupbhowmik8505Ай бұрын
Very nicely explained. Thank you
@diamondalaska6434Ай бұрын
bro is literally inconceivably awesome
@NA245thАй бұрын
Thank you, very well explained. Now I have to go back and examine my db. Thanks again
@fatihcaglar5516Ай бұрын
great explanation. thanks <3
@fatihcaglar5516Ай бұрын
these videos are great. please start again...
@jogsonmsabaha6324Ай бұрын
this is the best site i have ever seen salute to you
@astrojay5899Ай бұрын
any WGU students here?
@algasimjallow2414Ай бұрын
Struggled to understand normalization. But after watching this video it all just makes sense. Very great explanation and examples 👌
@OK-iw5imАй бұрын
Amazing
@bobvance9519Ай бұрын
excellent
@lamalamalamalamapapaАй бұрын
Wonderful Explanation!!! I was struggle trying to understand BCNF. And I have googled my ass off. Searching in stackoverflow. Finally, I found an acceptable one. Thank you!
@throwaway-lo4zwАй бұрын
im confused mate, shouldn't the primary key be unique? why do we have duplicate ids