Re: Building the virtual OTLT

From: Dan <guntermann_at_verizon.com>
Date: Fri, 10 Sep 2004 16:26:48 GMT
Message-ID: <cBk0d.116$5t4.64_at_trnddc01>


"Alan" <alan_at_erols.com> wrote in message news:2qb63bFtfdhiU1_at_uni-berlin.de...
>
> "Laconic2" <laconic2_at_comcast.net> wrote in message
> news:986dndg5yt7Hwt3cRVn-sg_at_comcast.com...
> > A few years ago, I was at a client site, dealing with the BANNER
> > application.

[snip]

> > These 185 selects were spearated by 184 "UNION" operators. There you
have
> > it. The mother of all unions, representing a virtual OTLT. I didn't
> > define a view, because I didn't have CREATE privileges on BANNER (a
good
> > idea, IMO but that's another discussion). But it isn't hard to simulate
a
> > view in scripts if you know what you are doing.
> >
> > Now all I have to do is query this monster for a code value of "R73",
and
> > it gives me the metadata I need to find R73 in BANNER, and a
description
> > that may make sense to the humans. Hurray!
> >
[snip]
> >
> > So the virtual OTLT can be a useful tool, even though it illustrates
bad
> > data management.
> >
>
> I would say that you have the perfect setup. Individual LTs, which makes
the
> data management correct, and a "view" of the whole shebang for certain
> practical purposes.
>
>
I'd agree whole heartedly with Alan's sentiments.

Dan Received on Fri Sep 10 2004 - 18:26:48 CEST

Original text of this message