3 ms·
I have worked with recurring events, and the answer that I've seen is generally both. You have one record which is the "template" and then populate the database
by was_boring 8y ago
I have worked with recurring events, and the answer that I've seen is generally both. You have one record which is the "template" and then populate the database out with specific instances to some arbitrary date. Every so often then run a cron to populate further and further out.
- mooreds 8y agoThat's pretty much what I did, but the original record wasn't stored in the DB, just the specific instances. Our use case was such that folks were moving around events periodically (it was a scheduling app), so we rarely had anyone "run off the end" of their repeated events.