From: Frank Swarbrick on
Interesting idea. Thanks!
Frank
--

Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403


n 10/8/2009 at 7:28 PM, in message
<e573ddfd-a026-4bd8-b0f8-ebbc526e3f52(a)z34g2000vbl.googlegroups.com>,
--CELKO--<jcelko212(a)earthlink.net> wrote:
> A trick I have is a look-up table with one column of type DATE, and
> one or more columns of various date-as-string CHAR(n) columns. Build
> a century with a spreadsheet and a text editor in 10 minutes or less.
> OUTER JOIN to it and the bad strings are NULLs.
From: Lennart on
On 14 Okt, 01:37, "Frank Swarbrick" <Frank.Swarbr...(a)efirstbank.com>
wrote:
> Interesting idea.  Thanks!
> Frank
> --
>
> Frank Swarbrick
> Applications Architect - Mainframe Applications Development
> FirstBank Data Corporation - Lakewood, CO  USA
> P: 303-235-1403
>
> n 10/8/2009 at 7:28 PM, in message
> <e573ddfd-a026-4bd8-b0f8-ebbc526e3...(a)z34g2000vbl.googlegroups.com>,
>
> --CELKO--<jcelko...(a)earthlink.net> wrote:
> > A trick I have is a look-up table with one column of type DATE, and
> > one or more columns of various date-as-string CHAR(n) columns.  Build
> > a century with a spreadsheet and a text editor in 10 minutes or less.
> > OUTER JOIN to it and the bad strings  are NULLs.

There's an earlier thread discussing this. You might find some
interest in it:

http://groups.google.se/group/comp.databases.ibm-db2/tree/browse_frm/thread/b2d4cc44f3e4e734/e00fdef508818c4e?rnum=1

/Lennart

From: Philipp Post on
Frank,

> I guess I should ask the question I don't want to ask <

I think it really depends on what you aim to do. If it is just some
sort of change log where you look at if you would like to find out
which user changed what and when, putting all in one table might not
hurt you, but if you would like to do other things it might be a
problem (as your example shows).

The following reading of Dr. Snodgrass might be of interest to you -
if not already known. He treats history tables and re-creation of data
from them very detailed.

http://www.cs.arizona.edu/~rts/tdbbook.pdf

brgds

Philipp Post