Re: FW: bitemporal functionality for PostgreSQL

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: FW: bitemporal functionality for PostgreSQL
Date: 2008-02-04 22:25:23
Message-ID: 1202163923.10057.817.camel@dogma.ljc.laika.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2008-02-04 at 20:50 +0000, Heikki Linnakangas wrote:
> Jeff Davis wrote:
> > Also, they use "period" to mean interval, and "interval" to mean
> > duration -- which is wrong, in my opinion; interval already has a well-
> > defined mathematical meaning.
>
> Agreed, but that mistake actually originates from the SQL standard. The
> SQL INTERVAL data type is really a duration, so I guess they had to come
> up with a new term for interval in the mathematical meaning.

Fair enough. However, that is just an example of the SQL idiosyncrasies
that I was referring to.

I think that kind of thing gets in the way a lot more than it helps,
which is why I found Temporal Data and the Relational Model so
refreshing.

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gevik Babakhani 2008-02-04 23:48:25 TODO item:Allow to_date() and to_timestamp() accept localized month names
Previous Message Peter Eisentraut 2008-02-04 22:16:07 Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59