[Fwd: Time stamping updates/inserts on records]

This is a multi-part message in MIME format. --------------83C26643E2085E8593E3D6B2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------83C26643E2085E8593E3D6B2 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Path: kannews!kannews!not-for-mail From: Bogdan Neagu <bogdan.neagu@alcatel.com> Newsgroups: comp.databases.informix Subject: Time stamping updates/inserts on records Date: Thu, 02 Nov 2000 11:54:54 -0500 Organization: Alcatel CID Message-ID: <3A019C5E.A9ADBE30@alcatel.com> NNTP-Posting-Host: gmoney.ca.newbridge.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: kannews.ca.newbridge.com 973184094 28884 138.120.137.230 (2 Nov 2000 16:54:54 GMT) X-Complaints-To: news@newbridge.com NNTP-Posting-Date: 2 Nov 2000 16:54:54 GMT X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en Xref: kannews comp.databases.informix:34265 Hi all. We are looking for an efficient way of time stamping inserts / updates on the records. We will also think to have an index on the time stamp. The tables can have millions of records, and the data can be fairly volatile (lots of inserts/updates). I have some questions to youy guys: 1. What will be an efficient way of doing this (adding a DATETIME, an integer with let's say seconds since January 1, 2000) ? 2. Since the time stamp always grows, will the index re-generation be fast, since only grows the B-tree in one direction ? Any help will be appreciated. Thanks, Bogdan Neagu --------------83C26643E2085E8593E3D6B2--

Sorry, guys, I did not post MIME, I just forwarded to informix-list@iiug.org without knowing it will get back here MIME'd. Bogdan Neagu