× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Paul,

since we have to deal with validity everyday we developed this structure:

Each row has an ID and we store the ID in others tables so we have direct
and stable links. This is the core of the concept.
Each row has two dates (can be timestamps if you prefer): initial and final
validity, both of them nullable. Initial date NULL means open period
(downward). Final date NULL means open period (upward) and marks CURRENT
period.

We use a trigger BEFORE with ACTGROUP(*NEW) to monitor invalid updates /
writes. Valid means no overlapping, adjacent, only 1 null allowed in a
collumn and so on.

HTH

--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco

2015-01-16 15:09 GMT+01:00 Charles Wilt <charles.wilt@xxxxxxxxx>:

[question posted in WEB400]
What's you're talking about is a "temporal database"
https://en.wikipedia.org/wiki/Temporal_database

Joe Celko has some good discussions online and in his books around them.

Charles



On Thu, Jan 15, 2015 at 8:51 PM, Holm, Paul <pholm@xxxxxxxxxxxxxxxxx>
wrote:

Hi,

Looking for design ideas or experience with the following.

We are creating a DB to hold equipment where each record holds a
description of equipment. They want to have the ability to have 1 to
many
"versions" of the record. For example, if a device firmware or
configuration is updated, they want to maintain the old record.

I'm thinking I can accomplish all this by simply adding a "Version"
column
to the database. Version could have values such as "1.0", "1.2", or
*CURRENT if it's the latest. When a new version is needed, we simply
copy
the record and update the VERSION field.

Feedback with this approach?

Thanks in advance, Paul
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.