E
eddiec
hi everyone,
I am designing a pallet management system. Many items are placed onto one
pallet. The items are all unique and have distinct features. Now, as far as
application design is concerned the most intuitive way of handling this
would be to have a Pallet object that holds an array of Item objects, which
reflects the situation in real life. As far as database design is concerned,
however, it is easier for the item to 'know' which pallet it belongs to.
e.g. I would create a table for the individual items where one of the
fields is palletID.
So what do I do? It would be very confusing (I think) to have different
design approaches in the application and in the database schema.
TIA
eddiec
I am designing a pallet management system. Many items are placed onto one
pallet. The items are all unique and have distinct features. Now, as far as
application design is concerned the most intuitive way of handling this
would be to have a Pallet object that holds an array of Item objects, which
reflects the situation in real life. As far as database design is concerned,
however, it is easier for the item to 'know' which pallet it belongs to.
e.g. I would create a table for the individual items where one of the
fields is palletID.
So what do I do? It would be very confusing (I think) to have different
design approaches in the application and in the database schema.
TIA
eddiec