DB2 Temporal Support: A Practical Introduction

Support for the declaration and manipulation of temporal data was added to the SQL standards in the revision of the standard formally adopted in December 2011 (SQL:2011 and ISO/IEC 9075:2011). Since then support has been added in both DB2 for z/OS (10 onwards) and DB2 for LUW (V10.1 onward). In this article we introduce DB2's temporal support through some practical use cases. 

Click here to read the full article

3 Comments
2 Likes

Why 30th not 31st December?

August 5, 2014 10:34 PM by Greg Palgrave

I may have missed it in the article, but I can't see where this was explained.


A quick search hints that DB2 uses 9999-12-30-00.00.00.000000 to indicate that the rows are current rows. (I'm sure it's buried in the manuals somewhere but I haven't found it yet.)

9999-12-30

August 6, 2014 03:16 PM by Daniel Luksetich

This is the all new IBM "end of the world" date as 9999-12-31 would cause an overflow when certain timezones are applied.

Add userid column in history table ?

August 19, 2014 06:05 AM by Nicolas VOLLMER

Hi,


Does history table record the used-id of the transaction ?


regards,
Nicolas

Recent Stories
Selecting Appropriate Data Architecture Technologies

SQL Tuning for Developers – Part 2 Explain Output

Some of my favorite tunings tips and tricks for DB2 by Joe Geller