this is a big question and i'm not trying to get you to do my modelling 
for me, but if anyone has experience with this i'd appreciate being 
pointed in the right direction:
How could one efficiently manage time slots in a dB? I mean for example 
telling the dB that Mike can be somewhere at 6:15 or 6:30 but not 6:45, 
and that Cynthia can be there at 6:15 or 7:00...
...and so on
my instinct is to create a "timeslots" table, but it looks like it would 
contain 35,040 records (one for each 15-minute period in the year). 
egad! The alternative is to create timeslots a month at a time or 
something, but the table would have to be reformulated every month.

any thoughts? feel free to get philosophical about it.


PHP Database Mailing List (
To unsubscribe, visit:

Reply via email to