Message-ID: <455300C3.4050008@archonet.com>
Date: Thu, 09 Nov 2006 10:19:47 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060918)
MIME-Version: 1.0
To: operationsengineer1@yahoo.com
Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: [SQL] [ADMIN] Is there anyway to...
References: <20061109012417.34765.qmail@web33310.mail.mud.yahoo.com>
In-Reply-To: <20061109012417.34765.qmail@web33310.mail.mud.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

operationsengineer1@yahoo.com wrote:
> i'm wanting to learn something here so i'm going to
> chime in.
> 
> the way i read what you are saying is that you'd have
> start_date and number_days columns in your table.
> 
> each day a query would run and pull the start_date and
> numbers_days columns.
> 
> the application (or postgresql function) would then
> take the current date, subtract starte date and
> compare it to number of days.  if it is above that
> number, the code will take some sort of action.
> 
> is that about it or have i missed something?

I think that's what Jim's talking about. Databases are good at filtering 
large numbers of rows.

You'll also want some sort of status code or "processed" flag, so you 
know not to look at rows you've already handled.

The other alternative would be an "expiry_list" table that stores the 
target row's key and when it expires. Add a row when the contract is 
created. Delete the row when the contract is paid. Keep it all 
up-to-date with triggers.

-- 
   Richard Huxton
   Archonet Ltd