in reply to Re^2: (OT) designing a "per event, resource schedule" manager
in thread (OT) designing a "per event, resource schedule" manager

if we have unix time 23 through 32 (excuse me).. and an inquiry for time 31-34 was made.. we can simply detect that $requested_start < $last_registered_end Thus a collission is present.

Ah, but how about back-to-back appts., where you start before one, and end before the other? Or a new appt. that "embeds", i.e. it has a start time after, and an end time before, another pre-existing appt?

My feeling is that scheduling is a pretty complex set of rules...but I'd be thrilled to be proven wrong.

----Asim, known to some as Woodrow.

  • Comment on Re^3: (OT) designing a "per event, resource schedule" manager