If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Table design question
Hi All,
I just wanted to see if the design of some fields in the table are standard practice. The database admin set up a Code_Desc table with fields Code_Type_ID, Code_Value and Code_Desc Code_Desc Code_Type_ID, Code_Value, Code_Desc 1 1 Emp Status - Active 1 2 Emp Status - Inactive 2 1 Emp Type - Associate 2 2 Emp Type - Manager 2 3 Emp Type - Auditor 3 1 Error Type - Major 3 2 Error Type - Minor 4 1 Shift - 1st 4 2 Shift - 2nd etc... However in tables that use these values she is wanting the Code_Type_ID and Code_Value combined. Example: Audit_History (table) Shift, Error_ID, Emp_Type (fields) 41 32 21 (combined) Is this standard? Is this the best approach? To me it adds coding by having to combine everything, but it also makes it hard for others to run queries on the Db that have limited query skills. Do you see other pitfalls besides the one I see? What is the best way to combine it as well, concatenation? |
Thread Tools | |
Display Modes | |
|
|