On Wed, Mar 08, 2006 at 12:56:38 -0300,
Rodrigo Sakai <[EMAIL PROTECTED]> wrote:
> Ok, but actually I'm not concerned about logging old values. I'm concerned
> about checking temporal constraints. Entity Integrity (PK) and Referential
> Integrity (FK).
Did you see the reference to 'Developing
attention!!
- Original Message -
From: "Brad Nicholson" <[EMAIL PROTECTED]>
To: "Simon Riggs" <[EMAIL PROTECTED]>
Cc: "Rodrigo Sakai" <[EMAIL PROTECTED]>; "Michael Glaesemann"
<[EMAIL PROTECTED]>;
Sent: Friday, February 24, 2006 1
ai" <[EMAIL PROTECTED]>
Cc: "Michael Glaesemann" <[EMAIL PROTECTED]>;
Sent: Friday, February 24, 2006 8:41 AM
Subject: Re: [GENERAL] Temporal Databases
On Fri, 2006-02-24 at 00:20 -0300, Rodrigo Sakai wrote:
It's a good solution, but not what I'm looking for.
I&#x
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED]
("[EMAIL PROTECTED]") transmitted:
> I have a somehow related question to this topic: is it possible to
> know (in postgresql) if an update on a column is absolute (set col =
> 3) or relative to it's previous value (set col =
hello,
I have a somehow related question to this topic: is it possible to know
(in postgresql) if an update on a column is absolute (set col = 3) or
relative to it's previous value (set col = col + 3)
in a trigger one have access to OLD row values and NEW row values, but
no correlation betwee
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] ("Jim C. Nasby")
wrote:
> On Fri, Feb 24, 2006 at 11:56:58AM -0500, Brad Nicholson wrote:
>> Simon Riggs wrote:
>>
>> >A much easier way is to start a serialized transaction every 10 minutes
>> >and leave the transaction idle-in-transa
On Fri, Feb 24, 2006 at 11:56:58AM -0500, Brad Nicholson wrote:
> Simon Riggs wrote:
>
> >A much easier way is to start a serialized transaction every 10 minutes
> >and leave the transaction idle-in-transaction. If you decide you really
> >need to you can start requesting data through that transac
[EMAIL PROTECTED] (Bernhard Weisshuhn) writes:
> On Thu, Feb 23, 2006 at 03:34:36PM -0300, Rodrigo Sakai <[EMAIL PROTECTED]>
> wrote:
>> I'm focus on temporal databases (not temporary), and I want to know
>> if anyone here is studying this tecnologies too. So, we can
>> exchange knowlegment. Speci
Simon Riggs wrote:
A much easier way is to start a serialized transaction every 10 minutes
and leave the transaction idle-in-transaction. If you decide you really
need to you can start requesting data through that transaction, since it
can "see back in time" and you already know what the snapsho
On Fri, 2006-02-24 at 00:20 -0300, Rodrigo Sakai wrote:
> It's a good solution, but not what I'm looking for.
> I'm looking for something implemented inside the database, like the
> flashback functionality of oracle 10g.
I think you need to be clear about why you want this: do you want this
as a
chael, I will have a look on the Date's article.
- Original Message -
From: "Michael Glaesemann" <[EMAIL PROTECTED]>
To: "Rodrigo Sakai" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, February 23, 2006 10:43 PM
Subject: Re: [GENERAL] Temporal Databases
On
On Feb 24, 2006, at 3:34 , Rodrigo Sakai wrote:
I'm focus on temporal databases (not temporary), and I want to
know if anyone here is studying this tecnologies too. So, we can
exchange knowlegment. Specifically, anyone who is trying to
implement on postgresql the aspect of time (temporal
There is also a description of an implementation for timetravel
at http://www.varlena.com/GeneralBits/122.php
If you would like to discuss this further, please let me know.
I've know postgres's and illustra's timetravel implementations.
--elein
[EMAIL PROTECTED]
On Thu, Feb 23, 2006 at 10:52:13
On Thu, Feb 23, 2006 at 03:34:36PM -0300, Rodrigo Sakai <[EMAIL PROTECTED]>
wrote:
> I'm focus on temporal databases (not temporary), and I want to know if
> anyone here is studying this tecnologies too. So, we can exchange
> knowlegment. Specifically, anyone who is trying to implement on
:[EMAIL PROTECTED]] On Behalf Of Rodrigo Sakai
Sent: Thursday, February 23, 2006
10:35 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Temporal
Databases
Hi everyone,
I'm focus on temporal databases (not temporary), and I want to
know if anyone here is studying
Hi
everyone,
I'm
focus on temporal databases (not temporary), and I want to know if anyone here
is studying this tecnologies too. So, we can exchange knowlegment. Specifically,
anyone who is trying to implement on postgresql the aspect of time
(temporal).
These
researches are le
16 matches
Mail list logo
