What structure would be more reasonable to store temporarily unknown data? Initially we do not know some aspects of the data we are working with, but such aspects will be filled in at some point.
I am developing a database for product refurbishment, in which I have to store data such as customer, model, serial number, etc. (this part is working well so far).
Said database has to handle shipment of products (incoming - outgoing). There is no problem for the outgoing part because we already have the data, the problem we are facing is with the incoming aspect, since some customers send products as a bulk or lot, and we only receive a summary of the shipment (i.e., model and quantity), other customers do send the complete information of the products.
Alternatives I have considered
So far, I have a
Shipment table, and a linking table that stores the relationship between
Shipments, the options that I have come up with are the following:
Option A. Insert products in the
Customer) and relate them to a
Shipment; later, when we receive the products we fill in the columns that were marked as
NULL. This option will allow the products to be treated as the rest and will add minimal changes to the system.
Option B. Have a separate table that stores the
ProductSummariesto be received, and then when the shipment is received they are properly stored in the
Producttable. This option will add more tables and complexity, but I will not have to deal with
Which of my two described approaches will be more suitable?
Is there any other design or structure that I can implement or follow?