DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=BSpdWWJAzq3Il4VGt7BULQoF95sF3ExUuwi/jaAjNjlzslP4S4CjWerl3IrD3RaEEtSEf/FiFIEtX1Bf7wbzPzfmjwkpKewBD5RFCnylYNcUwDFeVZSkwI4ccf7LmeQIvktYDzXoLHlt1M53MPD1j5Fio8wDXtezh+5NyhCOikQ=
	;
Message-ID: <20060618152846.49958.qmail@web31806.mail.mud.yahoo.com>
Date: Sun, 18 Jun 2006 08:28:46 -0700 (PDT)
From: Richard Broersma Jr <rabroersma@yahoo.com>
Subject: Re: any additional date_time functions?
To: Bruno Wolff III <bruno@wolff.to>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <20060618095450.GA29167@wolff.to>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

> > Are there any functions similar to date_trunc that can return variable increments i.e.:
> >  
> > 5, 10, or 15 minutes increments,
> > 3, 4, 6 hour increments,
> > 1, 2 weekly increments,
> You might be able to extract the time since the epoch and divide it by the
> appropiate number of seconds (the length of your interval) and truncate
> the result. This might have unexpected results for you when you span
> daylight savings time changes.
> 
> Another option is to not use timestamp, but rather just store an integer that
> represents some number of your intervals offset from an epoch.

Bruno,

Thanks for the suggestions.  I am going to "toy" around with them to see what I can get to work.

Thanks for the help.

Regards,

Richard Broersma Jr.