Kreig's advice is spot on! If you think the application through, I believe that you will come to the same conclusion.
It is poor database design to have implied or calculated occurrences of db records. It becomes impractical to modify the db schema in the future, say to add an attendee's reference (many to many child) to an implied record occurrence Also, it is poor application design -- it violates the law of parsimony: "The simplest way, is the best way" HTH Dick You could set an event table and a recurring event table-- or an event table with a recurring flag. No great problem so far On Wednesday, August 14, 2002, at 12:22 PM, Kreig Zimmerman wrote: > Having built a recurring events system myself, I found that the best > way to do it was to have all recurring events written to the DB, with > marker connecting them to the parent row. This is due to the overhead > of calculating these events for a dynanmic calendar format--if the rows > exist, it is simply a DB query; if not, these recurrences must be > re-created programatically each time events within a date range are > requested. > > Just my experience. It was difficult enough getting the recurring > events to work correctly! > ----- Original Message ----- > From: Seth Petry-Johnson > To: CF-Talk > Sent: Wednesday, August 14, 2002 1:23 PM > Subject: Recurring events in database driven calendar > > > Hello all, I am re-designing a database driven calendar application. > I want > to support recurring events (such as a weekly meeting) and I was > looking for > a few design suggestions. Basically, I want a user to be able to > enter an > event and specify that it happens on a repeating schedule: every > week, once > a month, etc. When a user views the calendar I want these to appear, > but I > do not want to have to enter a record into the database for each > occurrence > of that event. In other words, if an event happens weekly I want to > have > one database record, not a separate record for each week of each > month of > each year, etc. > > Does anyone have any experience with this sort of thing that they > would like > to share? I am specifically interested in the best way to store the > information about the repeat schedule in the database, and the most > efficient way to query against this data to find which events will > fall on > any given day. > > Thanks in advance, > Seth Petry-Johnson > Argo Enterprise and Associates > > > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
