Re: Building the virtual OTLT
Date: Fri, 10 Sep 2004 16:48:16 GMT
Message-ID: <kVk0d.17978$Lp5.11595_at_newssvr27.news.prodigy.com>
Another example when that kind of a table would be useful is logging. You want to report a bunch of events happening to different, but somehow related entities ( so they all have some kind of a parent entity this logging is tied to) . Each entity has its own set of event type codes, but there is only one event type code column in the log table, so you have a OTLT with just three columns (event type code, description, entity type) plus a bunch of lookup tables (one for each entity) - pretty much like what was discussed in the recent data consistency thread in this NG. Then, in the logging table, you have a foreign key pointing to the OTLT - and displaying the log becomes really easy - just a simple join.
"Laconic2" <laconic2_at_comcast.net> wrote in message news:986dndg5yt7Hwt3cRVn-sg_at_comcast.com...
> So the virtual OTLT can be a useful tool, even though it illustrates bad
> data management.
>
>
>
>
>
>
>
>
>
>
>
Received on Fri Sep 10 2004 - 18:48:16 CEST