Recurring Event Events VS Query Calendar Events Based on Recurrence Rules

I am creating specifications for a PHP / mySQL calendar application for a client. One of the issues that will need to be addressed is recurring events, the frequency of which is set by rules such as "every year on the first weekend, for which Sunday is in May." The client would like to be able to set rules such as "every third Thursday from March to June", etc.

The client requested that they be able to identify them rather than pre-populating a table of incidents of events with them over the next X years.

Are there any existing calendar solutions that allow for this kind of recurrence based on templates?

Is there any kind of calendar system request based on such rules rather than using parameters to generate recurring event incidents in the event table when the recurring event is created or updated?

What I am reading about this so far:

and. http://martinfowler.com/apsupp/recurring.pdf

b. http://www.kanzaki.com/docs/ical/recur.html

from. http://tools.ietf.org/html/rfc5545#page-37

etc. http://tools.ietf.org/html/rfc5545#section-3.8.5.3

e. iCal "Field" (for a database schema based on the iCal standard)

f. What's the best way to model recurring events in a calendar app?

g. http://en.wikipedia.org/wiki/ICalendar#Technical%5Fspecifications

h. http://muddybranch.thejkgroup.com/2005/01/why-remove-icalendar-recurring-rules/

I am. Should I store dates or recurrence rules in my database when creating a calendar app?

Note: This involves maintaining the repetition rules as well as keeping hard copies based on them for the next months.

J. Data structure for storing recurring events?

j. Should I store dates or recurrence rules in my database when I create my calendar application?

I am. Divide your data into two parts: "canonical" data (repetition rule) and "service" (generated dates, read-only, except regeneration). If the canonical data changes, restore the "serving" data at this point. For endless repetitions, keep a certain amount of copies and generate more if you're done (for example, if a user is looking at their 2020 calendar).

l. Recurring / Recurring Events Calendar is the best storage method Unique w and SQL response schema

i.e. https://github.com/tusharmath/sheql Language for repeating dates

etc. https://github.com/tplaner/When It looks BIG for generating dates according to rules including RRULE