Skip site navigation (1) Skip section navigation (2)

Re: SQL compliant interval implementation

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "Brendan Jurd" <direvus(at)gmail(dot)com>
Subject: Re: SQL compliant interval implementation
Date: 2006-05-23 22:16:31
Message-ID: 200605231516.32201.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Brendan,

> There are two classes of intervals. One class, called year-month
> intervals, has an express or implied datetime precision that includes
> no fields other than YEAR and MONTH, though not both are required. The
> other class, called day-time intervals, has an express or implied
> interval precision that can include any fields other than YEAR or
> MONTH.

Yeah, we used to do that.  It sucked.  In fact, most developers of 
applications which were calendar-heavy ended up using custom data types to 
work around the SQL-spec INTERVAL limitations.  And that benefits nobody.

We modified our INTERVAL type to function in ways that calendar application 
developers (of which there are several on this list) can actually use.  
See discussion leading up to the 8.0 release.

-- 
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

pgsql-hackers by date

Next:From: Brendan JurdDate: 2006-05-23 22:37:18
Subject: Re: SQL compliant interval implementation
Previous:From: Bruce MomjianDate: 2006-05-23 22:13:06
Subject: Re: [GENERAL] Querying libpq compile time options

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group