RE: Temporal database feature on IBM i?

Or the COMMON change request platform, both will work.  The COMMON one is
more likely to get traction.  

Also, If you know a member of the LUG (Large Users Group) you might get them
to put in the same request in that database too.  

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt
Olson
Sent: Monday, May 11, 2015 10:12 AM
To: Midrange Systems Technical Discussion
Subject: RE: Temporal database feature on IBM i?

Is this the correct way to submit enhancement requests or are we suppose to
use the DCR process (design change request)?



-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
Sent: Friday, May 08, 2015 2:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: Temporal database feature on IBM i?

You can always submit a requirement - the COMMON requirements site has been
improved and is available to everyone at

http://requirements.common.org

No login required anymore.

And you can go there on your smart phone - it behaves quite nicely.

Cheers
Vern

On 5/8/2015 1:17 PM, Alan Campin wrote:
> As far as I know the i Series is not getting this capability. It is 
> being made available for Windows and Unix but not for the iSeries. Bummer.
>
> On Fri, May 8, 2015 at 9:34 AM, Matt Olson <Matt.Olson@xxxxxxxx> wrote:
>
>> Midrange users,
>>
>> SQL 2016 will be introducing a temporal database feature which 
>> appears to be journaling on steroids.
>>
>> Apparently oracle already has this feature.
>>
>> Just wondering what is the feature equivalent on DB2 for the i?
>>
>> Here are screenshots of the feature:
>>
>>
>> http://i0.wp.com/blog.engineer-memo.com/wp-content/uploads/2015/05/im
>> age59.png
>>
>>
>> http://i1.wp.com/blog.engineer-memo.com/wp-content/uploads/2015/05/im
>> age61.png
>>
>> You basically add a clause to your SQL that says "FOR SYSTEM_TIME AS 
>> OF 'date/time value'" at the end of your SQL and voila, you get a 
>> picture of your table(s) as of a particular point in time. No reading 
>> cryptic squished together fields in journals, just natural queryable
data!
>>
>> Not only that you can "stretch" your database to the cloud, so all 
>> historical data is housed off site in presumably cheaper 
>> compute/storage infrastructure rather than your expensive on-premise 
>> database. Which makes sense for historical data since you are likely not
looking at it very often.
>> --
>> 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.
>>
>>

--
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.


--
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.