Database design regarding two 'linking' tables

Expand Post »

Hi all, im fairly new to database design and would just like a few tips if this is done correctly or if i can improve it..

Im mainly designing a 'leave' application and have an issue with regards to design of two linking tables..

First Table - [Request]
Username, DateStart, DateEnd, DayAmount

Second Table - [Log]
Username, DateStart, DateEnd, DayDate

basically the second table fills in the days of all the dates between the DateStart (starting date) and DateEnd (ending date)..

however im not sure if its good database design to use 3 columns as a primary key and if theres another easier way to solve this issue.

Thanks for your help

Similar Threads

Help with contact/mailing list database design... in Database Design
Database Design for storing versions in Database Design
Database Design feedback (absolute beginner here :) in Database Design
Inventory Control Database Design (Costing Methods) in Database Design
Database design - subtypes and instances of an entity in Database Design

Falzz

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

2 posts
since Jul 2007

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.

Previous Thread in Database Design Forum Timeline: Design Solution

Next Thread in Database Design Forum Timeline: Design question?

DaniWeb Message

Cancel Changes

User Name
Password