Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id F3100476598 for ; Fri, 24 Jan 2003 16:17:45 -0500 (EST) Received: from localhost.localdomain (unknown [216.31.142.3]) by postgresql.org (Postfix) with ESMTP id A8FF247742F for ; Fri, 24 Jan 2003 15:45:21 -0500 (EST) Received: from larubber.com (server [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with SMTP id h0OLJQP05921 for ; Fri, 24 Jan 2003 13:19:26 -0800 Received: from 10.1.86.1 (SquirrelMail authenticated user ddurst) by www.la-rubber.com with HTTP; Fri, 24 Jan 2003 13:19:26 -0800 (PST) Message-ID: <34244.10.1.86.1.1043443166.squirrel@www.la-rubber.com> Date: Fri, 24 Jan 2003 13:19:26 -0800 (PST) Subject: Re: Scheduling Events? From: "David Durst" To: In-Reply-To: <41705.216.86.192.34.1043397938.squirrel@www.la-rubber.com> References: <39409.216.86.192.34.1043367412.squirrel@www.la-rubber.com> <41705.216.86.192.34.1043397938.squirrel@www.la-rubber.com> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Reply-To: ddurst@larubber.com X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/404 X-Sequence-Number: 11269 here is a possible NON-Cron solution that a friend of mine came up w/ 1) Create a table w/ scheduled events and Account Ids attached to them. 2) Create a table w/ temporal event execution timestamps. 3) On journal entry check to see if there any schedule events for the Account 4) Check timestamp table for last execution If Last execution is out of range force execution Else continue as normal This is passive but it should allow for data integrity w/ out the need of a external system.