electronic leave concentration database design


i am now operative leave concentration (which subset e-scheduler project) i have database settlement follows:



event (event_id, dtstart, dtend... *follows icalendar standard*)

event_leave (event_id*, leave_type_id*, total_days)

_leave_type (leave_type_id, name, max_carry_forward)

_leave_allocation (leave_allocation_id, leave_type_id*, name, user_group_id, total_days, year)

_leave_carry_forward(leave_carry_forward_id, leave_type_id*, user_id, year)


does anyone here also operative an e-leave app? mind share your database settlement i am looking improved settlement mine. problem tide settlement wholly occurs during commencement year component calculating array days carried forward.



in sum i have run 1 + {$number_of users} * 2 queries (the initial out array allocation manners border lift disrespectful quota. following any user, i need out balance, following insert change database)



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

using mvc, should hoop communication between views? between models?