0 votes 0 votes Databases databases er-diagram + – Shivangi Parashar 2 asked Oct 22, 2018 Shivangi Parashar 2 1.4k views answer comment Share Follow See all 4 Comments See all 4 4 Comments reply Shivangi Parashar 2 commented Oct 22, 2018 reply Follow Share I think 1 would be the ans but given ans is 4 .Please correct me if I am wrong 0 votes 0 votes anonymous commented Oct 22, 2018 i edited by anonymous Oct 22, 2018 reply Follow Share The answer is 4. 3 for Entity and 1 for Multivalued Attribute. 1 votes 1 votes Verma Ashish commented Oct 22, 2018 reply Follow Share @dkm is there any problem if we merge two or more tables? Because FDs are not given and they talk only for 1nf. 0 votes 0 votes AkashChandraGupta commented Oct 7, 2019 reply Follow Share Here is the rule (https://db.grussell.org/section006.html#_Toc67114436): To map 1:m relationships, the primary key on the `one side' of the relationship is added to the `many side' as a foreign key. So simply merge the relations to the many side(N) even when it is total participation on both the side. Therefore, 3 table for Entity and Relation. 1 table for Multivalued Attribute in entity Bank. 0 votes 0 votes Please log in or register to add a comment.
1 votes 1 votes Table 1: Bank(Code, Ph_No) Table 2: Bank_Branches_BankBranch(Code, Name, Addr, Branch_No, BB.Addr) Table 3: Loan_Loans(Loan_No, Amount, Type, Branch_No) According to me there should be 3 tables Please correct me where I'm wrong Priyanka17 answered Oct 22, 2018 Priyanka17 comment Share Follow See all 5 Comments See all 5 5 Comments reply Show 2 previous comments Verma Ashish commented Oct 22, 2018 reply Follow Share Multivalued and composite both type of attributes are not allowed in 1nf. So for multivalued attributes 1 extra table is required. 0 votes 0 votes Soumya Tiwari commented Oct 22, 2018 reply Follow Share Composite attribute will require separate table for 1NF due to atomicity property but for multivalued attribute it can be there in same table as atomicity property is preserved though there'll be redundancy. 0 votes 0 votes Verma Ashish commented Oct 22, 2018 reply Follow Share No.. Composite attributes can be broken into simple attributes and present in the same table whereas for multivalued attribute we require seperate table.. 0 votes 0 votes Please log in or register to add a comment.
0 votes 0 votes THE MINIMUM TABLE WILL BE 4 . 3 FOR ENTITY AND 1 FOR MULTIVALUED ATTRIBUTE(REMEMBER IN 1NF ALL THE ATTRIBUTE MUST BE ATOMIC BUT BANK NAME IN ABOVE QUESTION IS MULTIVALUED ATTRIBUTE SO WE HAVE TO CREATE EXTRA TABLE FOR THAT) adarsh_1997 answered Oct 22, 2018 • edited Oct 22, 2018 by adarsh_1997 adarsh_1997 comment Share Follow See all 7 Comments See all 7 7 Comments reply Show 4 previous comments Priyanka17 commented Oct 24, 2018 reply Follow Share it can still be merged even with 1:n relationship because of total participation on both sides 0 votes 0 votes adarsh_1997 commented Oct 24, 2018 reply Follow Share in case of 1:n relationship table can be merged unnecessarily when in question it is asked about maximum table. if there are two entity in 1:n relationship then it can be merged with the primary key of both sides in the new table referring to original table(acting as foreign key)but in that case 3 table will be needed . but share me if anywhere if it is mentioned but i m sure that your procedure is possible for 1:1 relationship only. 0 votes 0 votes Priyanka17 commented Oct 26, 2018 reply Follow Share https://gateoverflow.in/77410/doubt please go through this 0 votes 0 votes Please log in or register to add a comment.