Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9G0CZP82192 for ; Mon, 15 Oct 2001 20:12:35 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 148510; Mon, 15 Oct 2001 17:12:30 -0700 From: "Josh Berkus" Subject: Re: Cenceptual help needed - periodic events To: "Pat M" , pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 15 Oct 2001 17:12:30 -0700 Message-ID: In-Reply-To: <9q9dq9$pnp$1@news.tht.net> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200110/196 X-Sequence-Number: 5151 Pat, > I'm goofing around, designing a planned maintenance system. In a > couple of > weeks I'll be taking on the actual scheduling of tasks. How would you > experts out there approach this? I've beeen thinking I can approach > this two > ways. I'm working on a legal calendar system, and we're storing all events as rows in the database. However, in our case the reasons are overwhelming, since the rules on how new events are generated (aside from those entered by users) are complex enough to fill several pages. Calculating on the fly isn't conceivable. Also, all of our events are, at one level or another, dependant on a user-entered event. Thus we can make all auto-generated events "children" of the parent event and change them when the parent changes. I designed another system that was all auto-scheduling -- a weekly produce delivery system. In this system, we took the expedient of not generating any even more than a week ahead of time, and providing functions that would drop all events and then re-create them, Differently, in a time entry system I designed all of the due dates for timecards were calculated on the fly by a complex view. So it depends on the number and complexity of the rules you will be applying. If the rules are very complex and/or require procedural logic, you probably want to generate and store records. Otherwise, no. -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco