Re: Table Design for 2 similar table

How about the records have a 1-to-1 relationship but not mandatory. It means there may be start record while the stop record non exist or vice versa.
However, they don't have common but conflict attributes.

My purpose is to speed up the searching process and simply the program coding.
Do you have any recommendation for me ?

>
> I think it depends on what it is your trying to model and what the
> data will be used for.
>
> For example, if the start records and stop records are two components
> of some sort of transaction and you will be mainly interested in the
> data at that transaction level, I would be inclined to consider the
> transaction the entity and use just one table. However, if your
> primary interest is the stop and/or start records themselves, then I
> would consider them each to be their own entities and put them in
> their own tables.
>
> This is a bit simplistic, as other issues also need to be considered -
>
> Do the start/stop records have a 1-to-1 relationship?
> Will there be many start records without stop records and vice-versa?
> Do the records have any common but conflicting attributes?
> etc
>
> --
> Tim X.
> tcross (at) northnet com au
Received on Wed Dec 18 2002 - 01:55:31 CST