Re: Linking records together
Date: Thu, 24 Sep 2009 08:46:53 +0200
Message-ID: <4abb15e6$0$10685$703f8584_at_news.kpn.nl>
Thanks for the suggestions, I will definitely look into it.
"Malcolm Dew-Jones" <yf110_at_vtn1.victoria.tc.ca> wrote in message
news:4aba9ba1$1_at_news.victoria.tc.ca...
> PJ (pjv_dev.nospam_at_geenspam.hotmail.com) wrote:
> : Hi all,
>
> : We need to track work items across several existing applications. Items
> can
> : start as a document on disk, can be renamed or moved, converted to a
> task
> : in an application, until they reach a certain state. The applications
> know
> : nothing about preceding or following applications and there is no common
> : identifier for the items, which has always been a good thing.
>
> : My idea is to create a table for all events. Each application will
> record
> : their
> : own events. A minimum is one event per application with a starting and
> : finishing situation for that application. Example: "file \\folder1\x.doc
> was
> : moved to \\folder2\y.doc". Another application may follow up with
> : "\\folder2\y.doc was archived with id 12345". Each event will have a
> date
> : and time.
>
>
> Use connect by to join the entries and sys_connect_by_path to show each
> complete path.
>
> You will get extra entries such as
> e.g.
>
> A->B
> A->B->D
> A->B->D->X
>
> Filter that list so you only see the results where the end (e.g. X) does
> not have a next connection.
>
> CONNECT_BY_ISLEAF might help do that.
>
> CONNECT_BY_ROOT might be useful when displaying the end points.
>
> sys_connect_by_path might not even be required here.
>
Received on Thu Sep 24 2009 - 01:46:53 CDT