-
Normalization in tables
Hi all ,
let say I need to design a student online form have this kind of columns(give name, surName, UniversityNumber, feeOne feeTwo, feeThree, email , addrss, coditionOne, conditionTwo,...conditionTen reason, documentOne, documentTwo, ....document TendocumentThree, OfficerName timeOne, timTwo, ProcessStatus)
submit once , search many times -> search and update is the basic tasks , so Normalzation to what level is best for my need?
thank you
________
FORD LTD (AUSTRALIA) HISTORY
Last edited by sql; 03-06-2011 at 02:10 AM.
-
-
Originally Posted by skhanal
Shoot for at least 3 NF.
How about
student ( userId, name , surName, address , email, phone)
applyCatalogy ( catalogID,feeOne, freeTwo, FeeThree)
studentIfor(userId, CatalogID, ConditionOne, conditionTwo, reason, documenone, documentTwo...)
Thank you
________
AMC EAGLE
Last edited by sql; 03-06-2011 at 02:10 AM.
-
This is not 3 NF, you have repeating columns in applyCatagory and Studentfor tables.
-
Originally Posted by skhanal
This is not 3 NF, you have repeating columns in applyCatagory and Studentfor tables.
how will you do
thankyou
________
Honda cb250 g5
Last edited by sql; 03-06-2011 at 02:11 AM.
-
You need to split
applyCatalogy ( catalogID,feeOne, freeTwo, FeeThree)
studentIfor(userId, CatalogID, ConditionOne, conditionTwo, reason, documenone, documentTwo...)
tables into two tables, so that fee or conditions are in their own table. Then you associate them in existing tables.
applycategory(categoryid, feeid)
feetable(feeid, feedesc)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|