Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would suggest giving the ability to store 'time off' as specific dates with time ranges or as a pattern. I have worked on a couple of scheduling systems that had very complex ways of dealing with union rules and employee availablity and this is how we handled it.</p> <p>Either employee says I want day X from y to z off which is easy to check against or they could define patterns that they wanted or didn't want (eg. I dont want to work fridays) and then when scheduling you could check to see if applying them to a specific shift broke a set rule (day off) or did/didn't match a specific pattern.</p> <blockquote> <p>Also how should I store this data of each employee?</p> </blockquote> <p>Have a table for storing employee's specific exceptions. I want day X from y to z off. You have an employee a date and a time span. Pretty simple.</p> <p>As for the patterns you will need to come up with some type of schema. And have types or something.</p> <p>So you could have a type like 'weekly off pattern' that would store full days off for a week which could be stored as a simple string representing the days off: 1000001. Assuming the first bit is sunday, this would represent wanting weekends off. You could then store the pattern as string or something and then based on the defined type you would know how to deal with the string.</p> <p>It can be a very complex or simple problem, it just depends how much customization you need to allow for. Hopefully this gives you enough ideas to get you started.</p> <p>Automatic schedule generation is A LOT more complicated depending on the exceptions/rules you need to support.</p>
    singulars
    1. This table or related slice is empty.
    1. POEmployee Limitations
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKelsey
    1. USKelsey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COBasically a good design - but - I would invert this so that "time on" is what you store. This is after all what you are really interested in. Bit maps look attrative but can end up being a real pain. I would probably store this in a db as emp,available_from, avalable_to. This would give a manager the ability to query "whos in on Satautday Afternoon'. Also bitmaps can only give you a here or not here data. Storing in a db gives you much richer options shuch as schedualed, avaialble , available only in emergency.
      singulars
      1. PO
      1. USJames Anderson
    2. COThe example I have was any pattern. You could store anything. Considering time on is more common than time off, I haven't seen any scheduling systems that store that for availability data. The point is to use patterns when not dealing with absolute data.
      singulars
      1. PO
      1. USKelsey
 

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