0

I am designing this database for a manufacturing company that produces boards for other factories to produce harnesses and I have created an items table, where each record is an item in the board to be produced, for example a fixture.

When a salesperson sees a client they fill up an information gathering format where each row of it represents one of the items to be produced. I've made a table for it.

This obviously is a one-to-many relationship, my question if I should create an intermediate table items_gatherings so as to keep the items table clean because it would have way too many fields, even if that generates a one-to-one relationship, especially considering that I also want to track the unique items through the supply chain. Also, should I also keep the tracking in another table?

Overall this are my questions:

  • Should I create a table for a one-to-many relation to keep attributes of the gathering separate from those of the item?
  • Should I do the same for other major busy categories of attributes of this table (e.g. item_production)?

Thank you for reading

Gibrán Vazquez
  • 54
  • 5
  • No - a one-to-many is a relationship like order items to order - the "order item" entity already contains all the details necessary and relevant, and it contains a foreign key to the "master" table of order. Absolutely no need and no benefit from introducing another "link" or "join" table here. Only in a many-to-many relationship, a relational model needs such a "join" or "link" table – marc_s Sep 10 '22 at 15:00

0 Answers0