ansaurus

Question

Help needed in database design for application of Timetable Generation

Answer 1

+1 A:

hm. looks like you also need relations between the teacher and the subject also - the Master can be left off safely in the names.

**standard**
standard_id
name

**teacher**
teacher_id
name

**subject**
subject_id
name

**subject_standard**
subject_id
standard_id
begin_date
end_date

**subject_teacher**
subject_id
teacher_id
begin_date
end_date

Randy 2010-05-08 20:32:21

Can you tell me the primary keys. Also wanted to know the use of begin_date and end_date in subject_standard and subject_teacer

Himadri 2010-05-09 19:13:04

@Randy I did not understand the purpose of rows begin_date and end_date

Himadri 2010-05-10 06:33:11

Usually, the begin date and end date can serve to capture all history for the relationshio. In this case, you will know something like TeacherA taught subjectA last year, but no longer teaches it this year. etc.

Randy 2010-05-10 15:40:50

as for primary keys, the id values should normally be numeric, unique, not null, and serve as the PK for each table. The joining tables do not have any good uniqueness to worry about - I assume you will allow more than one teacher to teach the same subject at one time.

Randy 2010-05-10 15:43:13

@Randy I don't need last year information. Just current year info.

Himadri 2010-05-11 04:21:16

ok - those are not mandatory - i just find that pattern useful in general.

Randy 2010-05-11 11:31:47

@Randy I can also merge subject_standard_teacher(subjectid,standardid,teacherid) and the primary key for this table must be combination of all three field. right?? Is there any other good option. Because, this is not normalized table.

Himadri 2010-05-12 06:04:08

ansaurus

tags:

views:

answers:

Help needed in database design for application of Timetable Generation

related questions