Search results

  1. M

    Atributes on the relationship 1:N or put them on entity (N)

    Ok, it is true. The real relationshipo is N:M, because when the employee finish his job, he can begin new project. Thanks a lot.
  2. M

    Typical situation 1:1 Superidentities with subidentities

    Thanks a lot for your answer. I can see this world is very complicated. No only the experience is very important, moreover they exist a lot of schools of notations. When i see all information in Internet, my head has a big explossion. I have a big luck finding this forum where all of you share...
  3. M

    Typical situation 1:1 Superidentities with subidentities

    Thanks for the answers. I am learning a lot of things with your help.
  4. M

    Typical situation 1:1 Superidentities with subidentities

    In this case, the bank offer only one account to retired people
  5. M

    Typical situation 1:1 Superidentities with subidentities

    Yes. your experience is GOLD. Thanks a lot.
  6. M

    Typical situation 1:1 Superidentities with subidentities

    Ok, is it possible conceptual design 1:1 and conceptual design other type?
  7. M

    Typical situation 1:1 Superidentities with subidentities

    do you recomend this type of ISA end in Access like only one table ACCOUNTS BANK and the specific atributes of specific accounts can be empty unless we have a lot of accounts with this atribute empty?.... Sorry for my english ;)
  8. M

    Typical situation 1:1 Superidentities with subidentities

    Hi. In all my questions you recomendme the 1:1 relationships are bad idea because in the real world dont exist or the implementation are very complicated. Now i am studying eer new types. Superidentities with subidenties. In ER the model would be this. This model is account bank types from...
  9. M

    Atributes on the relationship 1:N or put them on entity (N)

    I am trying it.. This world is very complicated for me ;)... Thanks a lot for your support. I am learning a lot of things with you and the others here...
  10. M

    Atributes on the relationship 1:N or put them on entity (N)

    The empleoyees can working on only 1 project. But several empleoyees not work any project. The projects have one or more workers. Hi. I wanted listen opinions about this model. 1º Question. Its better put the atributes worker's rol and begining date on the project, on the relationship or on the...
  11. M

    Adding attributes to a 1:N or 1:1 relationship. Consecuences?

    In Spain, people can have one DNI (National Identity Document) throughout their lifetime, and a DNI always belongs to a single person. The DNI cards are renewed every 5 years, and this is mandatory. Attached is the ER model that I think is suitable for this issue. I have included the 2 entities...
  12. M

    Adding attributes to a 1:N or 1:1 relationship. Consecuences?

    I need a tracking each renewal. This is the picture about this. My question si After this, when i put "date renovation" on relationship, change this the cardinality?, changing 1:1 to n:M? Thanks
  13. M

    Adding attributes to a 1:N or 1:1 relationship. Consecuences?

    I have doubts about what happens when adding attributes to a 1:N or 1:1 relationship. I understand that if I add attributes, in the relational model, this relationship would be treated as if it were an N:M relationship, creating a table for this purpose. For example, in a 1:1 relationship...
  14. M

    EER Model Trying

    Very nice help. Thanks. I am studying your information.
  15. M

    EER Model Trying

    Incredible answer. I am working in it. But i think you are an expert teacher with your explanations. Thanks a lot.
  16. M

    EER Model Trying

    Thanks for your recomendation of using google and youtube.
Back
Top Bottom