The Area being Modelled is :-
Subject: Payments Database Modeling
Question:
Goal: A database for tracking personal salaries from different jobs.

Explanation: I work two types of jobs.
For one job the work schedule is fixed, and the corresponding payments are on a regular monthly basis, periodically.

For the other type of jobs the schedule is quite irregular, and I get paid by hours.

Here is my dilemma.

If I use one master table to record every payment entry, I will have to decide either using hour or month as pay period intervals.

If I use hour as pay period interval, it will accommodate my ad hoc jobs nicely but not for my regular job.

I will have to divide my monthly wage from regular job by the total working hours in that month.

Not only would it make the table clutter, it would also demand a lot of repeating input for periodic information
(e.g. 9am to 10am; 10am to 11am....for everyday!) with exactly the same values.

On the other hand, if I make the payment interval monthly instead of hourly, it will definitely accommodate my
regular job better, but will lose a lot of information that I should keep track of for those ad hoc jobs.

I could make two different tables but I suspect that would make JOIN very complicated without resorting triggers.

Is there any templates or reference that tackles similar problem ?

Any suggestion would be highly appreciated.

Thanks.