chas wrote:
just as a side note, you might want to think about the nature of the events. i've found that it's better to stick with rdb for events-listings because my events fall into 3 categories when it comes to the dates/times :
a) one-off events. eg. you specify the dates. eg. 19 oct 1999, 2 nov 1999 for event A 1 nov 1999 for event B .... which results in a one-to-many relationship
b) regular events. eg. each monday, wednesday and friday for event D each saturday at 4 pm for event E this is ok in zope
c) between 2 dates. eg. starts on 2 october and ends 28 october. this is ok in zope too
How about an abstract Event class. The class should have a method that given a date returns true/false depending if the event occurs on that date. Now you just subclass as needed to support recurring, one-off or ranges Event objects. Would this work? Could you then use ZCatalog to find all events occuring on a certain date? -- Itamar - itamars@ibm.net ---------------------------o----------------------------------------------o Perl/Gimp Greeting Cards | Trust? Ha! The US dollar is backed by ICBMs! | http://www.sealingwax.com | --Anonymous Coward, Slashdot |