Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would go with three-table Kimball star (Date, Employee, Schedule), because sooner or later you will be asked to create (demanding) reports out of this. Who worked most nights? Who worked most weekends? Who never works weekends? Why am I always scheduled Friday afternoon? On which day of a week are certain employees most likely not to show up? Etc, etc...</p> <p>Tables would be:</p> <p><code>TABLE dimDate (KeyDate, FullDate, DayOfWeek, DayNumberInWeek, IsHoliday,... more here)</code><br/> You can pre-fill dimDate table for 10 years, or so -- may need to tweek the "IsHoliday" column from time to time.</p> <p>Employee table also changes (relatively) rarely.<br/> <code>TABLE dimEmployee (KeyEmployee, FirstName, LastName, Age, ... more here)</code><br/></p> <p>Schedule table is where you would fill-in the work schedule, I have also suggested "HoursOfWork" for each shift, this way it is easy to aggregate hours in reports, like: "How many hours did John Doe work last year on holidays?"</p> <p><code>TABLE factSchedule ( <br/>KeySchedule, -- surrogate PK <br/>KeyDate, -- FK to dimDate table <br/>KeyEmployee, -- FK to dimEmployee table <br/>Shift, -- shift number (degenerate dimension) <br/>HoursOfWork, -- number of work hours in that shift <br/>)</code><br/></p> <p>Instead of having the surrogate KeySchedule, you could also combine KeyDate, KeyEmployee and Shift into a composite primary key to make sure you can not schedule same person on the same shift the same day. Check this on the application layer if the surrogate key is used.<br/> When querying, join tables like:</p> <p><code> SELECT SUM(s.HoursOfWork)<br/> FROM factSchedule AS s <br/>JOIN dimDate AS d ON s.KeyDate = d.KeyDate <br/>JOIN dimEmployee AS e ON s.KeyEmployee = e.KeyEmployee <br/>WHERE <br/>e.FirstName='John' AND e.LastName='Doe' <br/>AND d.Year = 2009 AND d.IsHoliday ='Yes';</code></p> <p>If using MySQL it is OK to use MyISAM for storage engine and implement your foreign keys (FK) as "logical only" -- use the application layer to take care of referential integrity.</p> <p>Hope this helps. <br/><br/></p> <p><a href="https://i.stack.imgur.com/YKGjk.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/YKGjk.png" alt="empschd_model_01"></a></p>
    singulars
    1. This table or related slice is empty.
    1. POScheduling Employees - what data structure to use?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDamir Sudarevic
    1. USDamir Sudarevic
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POScheduling Employees - what data structure to use?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, trying to implement something similar.
      singulars
      1. PO
      1. USM_1
    2. COI have published a model here: http://www.damirsystems.com/?p=466
      singulars
      1. PO
      1. USDamir Sudarevic
    3. COThank you very much for the advise, I started writing webapp in django basing on your design. It's very helpful. Thanks a lot again :)
      singulars
      1. PO
      1. USM_1
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload