|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
design ideas for quantity and reserved amount of items
Basically I have a list of cables, a quantity, an available, and then location of the cable
so let's say I have an XLR cable XLR 5 total 3 available and then lets say 1 is in Japan and 1 is in Atlanta. I'm trying to think of the best way to represent this in tables and have come up with several ideas. The one i like best so far is a TABLE 1: cable quantity available TABLE 2: ID cable 1: cable 2: cable 3: location: Table 2's cable 1,2,3 is the quantity for how much they have checked out. I know this has to be bad database design, does anyone have any sugguestions? for example I'm sure i'd want to have a 3rd table to represent the many to many for cables to locations instead in which case for example table 3 cable location quantity but that'd be a lot of columns if i have a lot of cables, is this the best design? Because once they're returned from the location i don't really need that location anymore and it could actually be deleted from the database, all i really need is to keep track of the total amoutn of cables, available, and where they are. Last edited by unatratnag : October 17th, 2003 at 02:09 PM. |
![]() |
| Viewing: Dev Shed Forums > Databases > Database Management > design ideas for quantity and reserved amount of items |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|