Our schedule has seen good uptake in usage with our user base. Currently, we have around 4,000 events in our DB, with about 1/4 of those being recurring events.
The problem is that - at this point - I don’t know which of those recurring events (REs) will show as occurrences in the schedule time frame, and as a result I have to select all REs from the DB and send all of those to the client. This is OK for now, but as time goes on it is not sustainable - as the number of RE’s increases, the time to fetch those from the DB, process them for the client, and then send to the client will consume too much time.
There are 2 ways that this problem might be alleviated:
Fetch all REs from the DB. Then, process them - on the server - using RRULE logic to determine which of those will show occurrences in the current schedule start/end span.
Add procedural logic to the DB to execute RRULE logic, so that only REs with occurrences are returned with the DB fetch action.
I don’t know if either of these will result in time savings, nor by how much.
Anyway, I wanted to see if anyone (user or Mobiscroll) has had experience with this problem, and what - if anything - worked for you.