0

This question already has an answer here:

this is the first time I have ever tried to design my own database, so I'm sorry if this is a bit of a stupid question.

I have been trying to figure out how to create a database to sort an inventory of stage equipment, so that I can know where items are at all times, with the hopes of eventually expanding this to a large scale, multiple venue scheme. (so that items can be shared between venues)

My problem is the storage of the items. Where each type of item will need a different set of fields, I don't think a single table is the best solution. For example, an item marked as a cable will need to hold it's connector type, length, and some notes about the condition, where fixtures might need the type of fixture, beam angle, power consumption, weight, ect...

So the question is, how exactly would I link all of my different types to one table where I can look up an ID number of an item and it returns the correct cable or fixture?

I have a visualization of the database, I'm not sure if I have made it correctly, however. DB diagram

marked as duplicate by MDCCL, John Eisbrener, Community Aug 11 at 18:19

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Browse other questions tagged or ask your own question.