DBMS - Weak Entity Set with Total Participation

Поділитися
Вставка
  • Опубліковано 24 жов 2024
  • DBMS - Weak Entity Set with Total Participation
    Watch more Videos at www.tutorialsp...
    Lecture By: Mr. Arnab Chakraborty, Tutorials Point India Private Limited

КОМЕНТАРІ • 31

  • @TutorialsPoint_
    @TutorialsPoint_  Рік тому

    To Get Certification, Click Here: bitly.ws/PXXy
    Use coupon "UA-cam12" to get ‘’FLAT 12%’’ OFF at Checkout.

  • @2222Kai2222
    @2222Kai2222 Рік тому +5

    Thanks! I know this is pretty basic stuff, but it's still pretty hard to understand when you're a beginner. You explained it very clearly and were much easier to understand than the previous videos I found.

  • @haliskara2879
    @haliskara2879 4 роки тому +6

    I think you should enable captions because i get hard time to understand this accent this course is very good but im not native in english

  • @antoniaangelopoulou4269
    @antoniaangelopoulou4269 4 роки тому +5

    Could you help us by making a weak entity strong??? Thank you!!! and Greetings from Greece

  • @ekabhiramgedela7145
    @ekabhiramgedela7145 6 місяців тому

    as per your perspective what is the meaning of "against"?

  • @soujipenugonda7159
    @soujipenugonda7159 6 років тому +6

    The relationship is many to one that means
    1. One loan can be pay in multiple payment s
    2. One payment number associated with only one loan numbers
    But in the above example you are using same payment I'd for multiple loan numbers how can it possible???

    • @JatanPassi
      @JatanPassi 6 років тому

      Well you got it a little wrong when he said "arrow is coming from many to one in this case" at 1:54 he was talking with respect to payment entity,it is simple actually when we say one to many that means one entity in "set A" is associated with many entities in "set B" now what if we consider "set B" to be our initial set instead of "set A" then the case becomes many to one it's just the matter of perspective nothing more, if you still don't get it just forget it and for simply understanding take this case as one to many

    • @abhishekkaushik8199
      @abhishekkaushik8199 5 років тому +1

      Payment id represents deposit slip number. He's using a single deposit slip which has slip number as 20 to pay for all the three loans at once. He's not using separate slips.

  • @oshawastaken
    @oshawastaken 2 роки тому

    holy shit u explained it so well ur a legend

  • @anishtec
    @anishtec Рік тому

    What happens if the amount is different?

  • @shanmadhushan8645
    @shanmadhushan8645 3 роки тому +1

    Good job..keep it up

  • @bhanudaykashyap4534
    @bhanudaykashyap4534 4 роки тому

    Just hit like for him.....
    Explained very well

  • @varkam1523
    @varkam1523 3 роки тому

    Thank you so much sir.

  • @farhanishraq5812
    @farhanishraq5812 Рік тому

    thank you so much for

  • @daminduliyanage
    @daminduliyanage 4 роки тому

    not sure if it is a different notation but isn't the arrow should be pointing towards the relationship ( and not the entity ) ?

  • @GemaPratamaAditya
    @GemaPratamaAditya 5 років тому +12

    watched this in 1.25x speed and it was perrect

  • @rowdy8951
    @rowdy8951 2 роки тому

    what is partial key

  • @MuhammadUmairShaykh
    @MuhammadUmairShaykh 5 місяців тому

    Great

  • @mohakchaudhary1981
    @mohakchaudhary1981 5 років тому

    Great explained..

  • @suryabhusal1527
    @suryabhusal1527 3 роки тому

    Consider hotel(name, id) and room(number, beds) entity.
    1. Hotel is strong entity.
    2. Room is weak entity as its existence depends on hotel.
    3. Many hotel can have a room with same room number but different bed numbers.
    4. How do you model that.
    What confused me in above scenario is:
    1. Its hard to find the room for specific hotel as two hotel have same room number.