MAIL PROTECTED]>;
Sent: Friday, April 15, 2005 5:23 PM
Subject: Re: Temporal databases & MySQL
What you describe makes sense and would certainly work, I don't know
that I would call it a temporal solution. The ENUM (I, U, D) seams a bit
redundant with time. This model resembles a trad
Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Daniel BODEA
Sent: Saturday, April 09, 2005 8:46 PM
To: mysql@lists.mysql.com
Subject: Re: Temporal databases & MySQL
I was thinking about the following model for the application I'm working
on:
Any given table T
Message -
From: <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.db.mysql.general
Sent: Wednesday, April 06, 2005 5:13 PM
Subject: RE: Re: Temporal databases & MySQL
There was a magazine "Database Programming & Design", now defunct...too
much detail for the average IT Manager so
I was thinking about the following model for the application I'm working on:
Any given table T holds the conventional data associated with instant NOW,
no temporal data at all. There are tables T_HIST for every table T with an
identical structure plus one date column which is set to NOW on every i
.com/vault/9810snod.html
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Daniel BODEA
Sent: Tuesday, April 05, 2005 11:11 AM
To: mysql@lists.mysql.com
Subject: Re: Temporal databases & MySQL
Hi Shawn,
I really meant temporal and not temporary. Temporal as in TSQ
Hi Shawn,
I really meant temporal and not temporary. Temporal as in TSQL2. Databases
that on the one hand accumulate all changes to data over time along with
accurate time information and on the other hand provide varying degrees of
transparency in querying this data based on the theory of instant
news <[EMAIL PROTECTED]> wrote on 04/04/2005 12:59:53 PM:
> Greetings everyone,
>
> I haven't been able to find any piece of information on temporal
databases
> and MySQL except the code from the TAU Project which seems to be
> experimental at best. Not even discussions on the mailing lists or o
