From: David Durst <ddurst@larubber.com>
To: pgsql-sql@postgresql.org
Subject: Re: Scheduling Events?
Date: Fri, 24 Jan 2003 13:19:26 -0800 (PST)
Message-ID: <34244.10.1.86.1.1043443166.squirrel@www.la-rubber.com> (raw)
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>
<Pine.LNX.4.44.0301240913220.11997-100000@matrix.gatewaynet.com>
<41705.216.86.192.34.1043397938.squirrel@www.la-rubber.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ddurst@larubber.com
Subject: Re: Scheduling Events?
In-Reply-To: <34244.10.1.86.1.1043443166.squirrel@www.la-rubber.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox