Re: seeking advise on DB tables, split or not split

"rob van laarhoven" <rob_at_dsdelft.nl> wrote

> Not by braking an entity into serveral pieces but by minimizing redundancy
> using normalization.

Rob,

This was what I meant/intended by "breaking into tables."

> If you have an object with 50 properties and it can not be normalized than
> IMHO it is best to create that table with 50 columns. I think breaking the
> table
> into pieces will make maintenance more complex (for example deleting one
> record will have to remove records from several tables).

I guess I find it pretty difficult to imagine an object with 50 attributes all independent of one another. What is this monster?

 > > Why are you recommending the bad ol' days, when we have tools now to  let
> > things be split into rational and sensible sub-sections, in this case
> > related tables
>
> The sugested method is not relational.

Yes, if you say so, then Mohammad's reply would make sense.

                                                          -dlj.