Please support our Database Design advertiser: Programming Forums
 |
•
•
Join Date: Jul 2007
Posts: 1
Reputation: 
Rep Power: 0
Solved Threads: 0
Newbie Poster
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
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
Other Threads in the Database Design Forum
- Database Design for storing versions (Database Design)
- Database Design feedback (absolute beginner here :) (Database Design)
- Inventory Control Database Design (Costing Methods) (Database Design)
- Help with contact/mailing list database design... (Database Design)
- Database design - subtypes and instances of an entity (Database Design)
- Database Design - Supertypes and Subtypes (Database Design)
- Database Design Advice (MySQL)
Other Threads in the Database Design Forum
- Previous Thread: Design Solution
- Next Thread: Design question?
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Linear Mode
