Re: DB design issue

> A system can have zero or more interface.
> An interface can have zero or more message.
> A message can have zero or more datafield with an ordered position.
> A datafield can be a simple one (like integer, float, etc)
> or composed by other datafield.
> Then I'm wondering about the db data model.

If the data can be as follows...

System1

   Interface1
   Interface2

      Msg1
      Msg2
         Field1 (simple)
         Field2 (simple)
         Field3 (complex)
             Field100 (simple)
             Field101 (simple)
             Field102 (complex)
                   Field200 (simple)
                   Field201 (siimple)

... maybe the following main tables will be needed:

T_System
T_Interface
T_Msg
T_Field (... isSimple? ...);
T_ParChildField

The most challenge part may be managing fields which can be composed of fields. Received on Sat Nov 18 2006 - 18:25:08 CET