|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Database Design, HELP !
I'm currently trying to design a database for a website I'm creating but im running into a few problems. Hopefully someone can help!
I have a "Lecturers" table which contains all their details, email ,name etc and a "Modules" table which contains Module Codes and Title's etc. The core problem i'm having in trying to include different features for different modules. Lets say I have one module that will have a news, a labs and a project feature(each of these features have their own separate tables aswell). Do I create a table called "Module" with the fields, moduleCode,newsID,labID,projectID ? I dont see how I can create a table of features, if each feature itself is a table with different fields to the next? Any idea's of how I should approach this are much appreciated ! |
|
#2
|
|||
|
|||
|
You might be in the similar Nested database structure situation
like what's listed in these forum:- http://forums.devshed.com/t64446/s.html http://forums.devshed.com/t74476/s.html that's one of the way to solve your problem. However, you could use the way u suggested. Module - moduleCode,newsID,labID,projectID Pro: - 'easier' to put data into your table - Don't have to use very complex query to link several fields or many tables to obtain result. (which Might reduce server load and faster access time) - "save time on normalizing your tables" - ..... etc Con: - Non-normalize table. - Bigger storage space. (repeated records forfeited the meaning of RDBMS) - ..... etc |
![]() |
| Viewing: Dev Shed Forums > Databases > Database Management > Database Design, HELP ! |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|