Re: Recursive or How?

> Database for a bug tracking system.
> Customer table
> Location table
> Call table
> One to many relationship exists between the Customer and Locations.
> Each record in the Call table may optionally have
> either a Customer or a Location as Parent.

An oodb like XDb gives the flexiblity to struture the data as shown below. Note, an object's class is shown in brackets and a property is preceeded by a dot. In XDb a property may have 0, 1, or many values.

Cust1[Cust]
  .Call
    Call1[Call]
    Call2[Call]
  Loc1[Loc]
    Call3[Call]
  Loc2[Loc]
    Call4[Call]

Cust2[Cust]
  .Call
    Call5[Call]
  Loc3[Loc]
    Call6[Call]
    Call7[Call]
  Loc4[Loc]
    Call8[Call]

Hypothetically, Call5 could be cut and pasted under Loc4 when the location becomes known. Oodb are especially well suited for logic that use recursion. Received on Thu Dec 20 2001 - 01:12:29 CET