danbarry commented on danbarry/recurring_events_for
Wed 11/5/2008 11:49pm
Comment in 2edd4db:
While this solution should work, it isn’t necessary to create both a bookings table and an events table. If you wanted to, you could change lines 11 and 21 of recurring_events_for.sql to have the function select from the bookings table instead of the events table. Your bookings table would then have to have all of the columns required by the function, but you could have them to default to null and forget about them.
If you want to keep your code base a little cleaner, you could make your own fork of the project to only include what you need. That could also be helpful later if you need to add some other type of recurrence logic.