recurring event with no end date

Hi there,

   I'm currently in the process of trying to implement recurring events in the scheduler with a completely custom lightbox... and consequently a custom server-side code, mainly INSERT, UPDATE and DELETE operations were all redefined by me. 

Now, setting aside the basic issues of putting the controls on the lightbox and adding the necessary fields in the database, I’m rather curious about something.

From what I understood, recurring events actually create multiple entries in the database with each “recurrence” having a pointer to the master event by ways of the PID field. This goes well with events having fixed reccurrence (like repeat 12 times and then stop)… but what happens when you decide to go with the “no end date” option? You can’t very well generate an infinite amount of events in the database. How does the scheduler treats this type of recurring events?

Anyway thanks in advance,

Osu

Not exactly.
When recurring event created - only one record is added to db. Record for master event.
Client side code, during data loading can decode rec_type string, and based on it multiple event instances can be rendered. It allows to use events with no-end-date, because we need only one record in DB for any count of events.

If event instance for some date must differ from master event ( has different text, or time ) - in such case we create an extra record in DB, linked to master through pid. Now during data loading, client side code will use pid linked event if it exists, and if there is no such linked event, will render instances of event, based on rec_type

Oh I see, so it’s the pattern that’s saved, not the events themselves (well aside from the master event of course). Thanks for the answer :slight_smile:.

Osu