[Info-ingres] Re: Fw: tid and the date a row originally came into a table

[Martin Bowes]

I suspect the tids would be sequential if the table was a heap table.

Marty

From: Allan Biggs <allanb4 at iname.com>
Sent: 29 May 2020 11:24
To: allan biggs <allan.biggs at gbr.dupont.com>; Ingres lists <info-ingres at lists.planetingres.org>; Martin Bowes <martin.bowes at ndph.ox.ac.uk>
Subject: Re: Re: [Info-ingres] Fw: tid and the date a row originally came into a table

Thanks, Marty

I learned a long time ago to avoid tids. It was just odd that in this case they managed to create a sequence!



--
Sent from my Android phone with mail.com<http://mail.com> Mail. Please excuse my brevity.
On 29/05/2020, 11:13 Martin Bowes <martin.bowes at ndph.ox.ac.uk> wrote:
Is the database journal enabled? Is the table journal enabled?

If yes to both then auditdb is your friend. You can execute this on a specific table and will then see all the insert, update, delete traffic on the table over the time window chosen.

This should give you the data you need to determine what the recent additions have been.

Marty

PS. NEVER rely on tids.

From: Allan Biggs <Allan.Biggs at GBR.dupont.com>
Sent: 28 May 2020 16:40
To: info-ingres at lists.planetingres.org
Subject: [Info-ingres] Fw: tid and the date a row originally came into a table

----- Forwarded by Allan Biggs/GB/CONT/DPT on 28/05/2020 16:39 -----

From:        Allan Biggs/GB/CONT/DPT
To:        openroad-users at googlegroups.com<mailto:openroad-users at googlegroups.com>, "info-ingres at lists.planetingres.org<mailto:info-ingres at lists.planetingres.org>" <info-ingres at lists.planetingres.org<mailto:info-ingres at lists.planetingres.org>>
Date:        28/05/2020 16:07
Subject:        Fw: tid and the date a row originally came into a table
________________________________




A colleague  has an issue with data being overwritten and some inserted by a feed from a plant system.

If we look at the table below rows above the cursor may have been updated with new results or just be values which were there in 2006.

the rows including the cursor row and below didn't have values in 2006 and have been inserted on 28-apr-2020

The issue is caused by the actual mill roll number recycling in the plant system (don't ask why) and the application which fills this table and others not realising that this is an old mill roll.

The data clearly should be archived off occasionally and there is a good reason why this didn't happen.

So here is the question - I / we assumed that rows inserted  (after 28-apr-2020) would have a recent tuple id but if we look at the table it's clear they don't.
We are pretty sure that the answer to our question - Is there a way of working out when these rows came into the system? - is that there isn't but we decided to ask anyway.  It surprised me that the tids were sequential.

The tuple ids for rows which have genuinely been added recently are considerably higher than the ones in this table.

BTW a quirk of the plant system means that  not every new mill roll after a certain time is a duplicate. In fact very few overlap.

If anyone has any ideas ...........

thanks
Allan & Benoit

[Image removed by sender.]

This communication is for use by the intended recipient and contains
information that may be Privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender by
return e-mail and delete this e-mail from your system. Unless explicitly
and conspicuously designated as "E-Contract Intended", this e-mail does
not constitute a contract offer, a contract amendment, or an acceptance
of a contract offer. This e-mail does not constitute a consent to the
use of sender's contact information for direct marketing purposes or for
transfers of data to third parties

Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean

          http://www.DuPont.com/corp/email_disclaimer.html
_______________________________________________ Info-ingres mailing list Info-ingres at lists.planetingres.org https://lists.planetingres.org/mailman/listinfo/info-ingres
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20200529/935e861c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 5498 bytes
Desc: image001.jpg
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20200529/935e861c/attachment.jpg>