Thank you so much sir for this great,clear and well understanding explaination ! It's my exam in 4 days and I was trying a similar question of yours and this video helped me reached far and far. Thank you sir, may god bless you in everything.
In ER (Entity-Relationship) mappings, derived attributes are typically not included as separate attributes in the entity model. Derived attributes are calculated or derived from other attributes in the entity, and they do not represent stored data in the database. Instead of including derived attributes in the entity model, they often calculated on-the-fly when needed or stored in a separate table or view. Including derived attributes in the entity model can lead to redundancy and potential data inconsistency.
Yes derived attributes will not be stored in database, but derived attribute values will be calculated based on already existing data. So in this relational mapping we will ignore derived attributes.
Watching this 2hrs before the exam, Thank you! Saved
Thank you so so so muchhhh, tomorrow's my exam and you've been really helpful with explaining
Do you have like this video but for other example? Library or hospital or something
Thank you so much sir for this great,clear and well understanding explaination ! It's my exam in 4 days and I was trying a similar question of yours and this video helped me reached far and far. Thank you sir, may god bless you in everything.
Thank you Harees
🚶
@@maheezthariq .....!
Lol rookie number ,i have exam in 20 minutes
Excellent video. Thank you for making it simple.
Thank you
You're doing great work Sir. It's really sad to see such low reach. Best of luck for future endeavours
Thank you Naeem
What a neat explanation!!
Thank you 🙏
Best explanation w.r.t (Ramez Elmasri, Fundamentals of Database Systems (7 th Edition)) book
Thank you
🔥🔥🔥
Great video dude ! 1000x Better than my prof.
Thanks Alot 🇱🇰❤️
THANK YOU SO MUCH SIR. THIS VIDEO IS VERY HELPFUL FOR ME ... LOVE FROM PAKISTAN 🇵🇰
Thank you sir
Thank you, watching this before my quiz
Same condition here bro
Best video on this topic
why didnt we consider dependents_of in the 1:N relationships?
@@adityasareen5638 that is already covered while covering weak entity dependent.
Please check from 4:50
Thank you sir.. You have explained it very well.
I can't getting😅😅
thank you sir! you saved me from the internals
THANK YOUUU
thank you very very very very very very much sir
Thank you 🙂
Yeah it’s really nice of you sir
thank you sir
Thank you so much! ☺
Well helped
DEPENDENTS OF is also 1:N relation but why we haven't included it
It is already covered while converting weak entity conversion
@@aksharacsit Thank u sir
thank you sir 😄😄
explained very well sir, thank you
Thanks sir 👍
Thank you
Thank you so much sir, such a great and understanding explanation
sir I want to ask do we always ignore the derived attribute
In ER (Entity-Relationship) mappings, derived attributes are typically not included as separate attributes in the entity model. Derived attributes are calculated or derived from other attributes in the entity, and they do not represent stored data in the database. Instead of including derived attributes in the entity model, they often calculated on-the-fly when needed or stored in a separate table or view. Including derived attributes in the entity model can lead to redundancy and potential data inconsistency.
Yes derived attributes will not be stored in database, but derived attribute values will be calculated based on already existing data. So in this relational mapping we will ignore derived attributes.
thank you
you are great sir g
Too perfect sir,awesome
Thank you
Thank you so much 🥰 Sir
nice
Thank u for wonderful video😊
Thank you so much sir 🤩
thank you so much
can u provide the text book link what u follow
Fundamentals of Database Systems
Book by Ramez Elmasri
@@aksharacsit if u don't mind please provide the text book link for easy download
Excellent work!
Sir what about weak entity
Weak entity starts at @ 4:15 minutes