pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Richard Broersma Jr <rabroersma@yahoo.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: any additional date_time functions?
Date: Sun, 18 Jun 2006 04:54:50 -0500
Message-ID: <20060618095450.GA29167@wolff.to> (raw)
In-Reply-To: <20060617200820.83165.qmail@web31805.mail.mud.yahoo.com>
References: <20060617200820.83165.qmail@web31805.mail.mud.yahoo.com>

On Sat, Jun 17, 2006 at 13:08:20 -0700,
  Richard Broersma Jr <rabroersma@yahoo.com> wrote:
> I am working with the date_trunc() function with great success especially in the group by clause
> for aggregates.
> 
> However, it is limited to returning "WHOLE" time units. i.e. years, months, days, hours, minutes,
> seconds.
> 
> 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,
> 
> I imagine that the returned values would have to either be the "floor" or "ceiling" of the actual
> time stamps.

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.



view thread (3+ messages)  latest in thread

Message-ID: <20060618095450.GA29167@wolff.to>
Permalink:  ../20060618095450.GA29167@wolff.to/
Also on:    postgresql.org/message-id/20060618095450.GA29167@wolff.to

 · 

reply

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: bruno@wolff.to, rabroersma@yahoo.com
  Subject: Re: any additional date_time functions?
  In-Reply-To: <20060618095450.GA29167@wolff.to>

* 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