Thanks, I like that better than the one I am working with. The one I am working with has had to have a lot of checking put in to handle possible date conflicts and things of that nature. I think the thought process on this one was to minimize the amount of rows put into tables. Seems to be a common thought process I run into and not sure where it originate from since guessing it comes from working with some older systems.
On 8/8/06, Denny Valliant <[EMAIL PROTECTED]> wrote: > > > > So in my case, there is only one event, with however many dates. > > tbl_events > :eventID > :eventDescription > > tbl_eventdatetimes > :eventDateID > :eventID > :eventDateTimeStart > :eventDateTimeStop > > Pretty much. Has worked well for calender stuff, where I'm looking for > conflicts > on a certain date, and don't want to have to check all event start dates > and > end > dates for dates & times within the given period, etc.. > > Could just be "six of one, half a dozen of another" though. > > T ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:249273 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
