On Mon, 2008-02-04 at 20:50 +, 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
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
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 du
On Sun, 2008-02-03 at 15:56 -0500, Greg Smith wrote:
> On Sun, 3 Feb 2008, Jeff Davis wrote:
>
> > I think what he means by "bitemporal" is what CJ Date, et al., refer to
> > as "fully temporal" (as opposed to semi-temporal), that is, dealing with
> > time intervals rather than time points.
>
> B
Le dimanche 03 février 2008, Greg Smith a écrit :
> On Sun, 3 Feb 2008, Jeff Davis wrote:
> > I think what he means by "bitemporal" is what CJ Date, et al., refer to
> > as "fully temporal" (as opposed to semi-temporal), that is, dealing with
> > time intervals rather than time points.
>
> >> I wou
On Sun, 3 Feb 2008, Jeff Davis wrote:
I think what he means by "bitemporal" is what CJ Date, et al., refer to
as "fully temporal" (as opposed to semi-temporal), that is, dealing with
time intervals rather than time points.
I think fully temporal is a step of complexity above how some people us
On Sun, 2008-02-03 at 10:48 +, Heikki Linnakangas wrote:
> I don't know what "bitemporal" is all about, but to me, the
> pgsql-temporal approach is clearly the most flexible and attractive.
I think what he means by "bitemporal" is what CJ Date, et al., refer to
as "fully temporal" (as oppos
Jeff Davis wrote:
On Fri, 2008-02-01 at 15:42 +, Luke Porter wrote:
All
Is there an interest in developing bitemporal functionality in
PostgreSQL
I am very interested in this topic, and I maintain the pgsql-temporal
project at:
http://pgfoundry.org/projects/temporal/
It's missing go
On Fri, 2008-02-01 at 15:42 +, Luke Porter wrote:
> All
>
> Is there an interest in developing bitemporal functionality in
> PostgreSQL
>
I am very interested in this topic, and I maintain the pgsql-temporal
project at:
http://pgfoundry.org/projects/temporal/
It's missing good docs and a
On Feb 1, 2008, at 10:42 AM, Luke Porter wrote:
All
Is there an interest in developing bitemporal functionality in
PostgreSQL
Regards
Luke
I can only speak for myself, but- definitely! Based on the googling I
did on "bitemporal database", I kind of do this already with
PostgreSQL. S
Luke Porter <[EMAIL PROTECTED]> writes:
> Is there an interest in developing bitemporal functionality in PostgreSQL
Is that anything like the late, mostly unlamented "time travel" feature?
regards, tom lane
PS: in general, defining what you want with one word and assuming
All
Is there an interest in developing bitemporal functionality in PostgreSQL
Regards
Luke > From: [EMAIL PROTECTED]> Subject: Re: bitemporal functionality for
PostgreSQL> To: [EMAIL PROTECTED]> Date: Fri, 1 Feb 2008 10:08:03 -0500> > Luke
Porter wrote:> > > > Bruce> > > > I have a compell
12 matches
Mail list logo
