Databases
StackOverflow2013
Postsdbo
POComments/Suggestions on database design - Warehouse Stock Management
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POComments/Suggestions on database design - Warehouse Stock Management
    primarykey
    data
    text
    <p>I'm currently creating a stock management system that uses multiple warehouses (with sub locations) and since this is my first big project I would love some feedback.</p> <p>Let me show you what I have done so far... <a href="http://i1251.photobucket.com/albums/hh551/stackoverflowtemp/Database.png" rel="nofollow">Link as Im still new here</a></p> <p>You first need to create a Warehouse, then you can create a Location within that Warehouse.</p> <p>You can also create an ItemType (ItemGroup), then you can create an Item for that group.</p> <p>Once you have an Item and Location you can add Stock, the Stock table has a composite key so that duplicates cant be added. I also added a constraint so that you could not enter an Item of the wrong ItemType, same constraint on the Warehouses/Location. </p> <p>I then need to keep records of each piece of stock, SerialisedItems and NonSerialisedItems. Example: If non serialised stock is added with a quantity of 10 then I currently create 10 rows inside the NonSerialisedItems table (1) that are set to ‘in stock’ with the relevant stock information. If they change the amount of stock then rows would be deleted or added (2).</p> <p>I could also do with a Van table somewhere that is similar to Warehouse, but think I would have to change the Warehouse table to something like Storage that references two tables, Warehouse and Van?</p> <p><em>(1) I currently have a TransactionScope on my page adding x number of rows, Is this the best way to handle that? (2) The Quantity amount in the Stock table would have to count the number of rows for that item and then update the Quantity each time stock is added or removed, any problems here?</em> - <strong>Both Questions Fixed - Only create rows for serialised items.</strong></p> <p><strong>Any other problems?</strong></p> <p>Well that’s what I have done, if its good or terrible let me know. Also if there are any pitfalls I should be looking out for that would also be great to know.</p> <p>Thanks</p> <p><strong>[EDIT]</strong> Thanks to Neville K I have made a few changes...</p> <p><a href="http://i1251.photobucket.com/albums/hh551/stackoverflowtemp/Database2.png" rel="nofollow">Link to new and improved database</a></p> <p>This seems to make a lot more sense! Think I had been staring at it to long yesterday!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USLuckyl337
    1. USLuckyl337
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POComments/Suggestions on database design - Warehouse Stock Management
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POComments/Suggestions on database design - Warehouse Stock Management
      1. USAryan SuryaWansi
      1. VTFavorite
    3. VO
      singulars
      1. POComments/Suggestions on database design - Warehouse Stock Management
      1. USPritesh
      1. VTFavorite
    1. CO(2) is definitely a bad idea. There might be items with *large* quantities, e.g. small screws. Even worse, you might have items like cables where the quantity can have fractions (310.25m)
      singulars
      1. POComments/Suggestions on database design - Warehouse Stock Management
      1. USErich Kitzmueller
    2. COThe large quantities is what I was worried about, I guess I can just create them as needed? And thanks I hadnt thought of cable, if cable is sold in meters I would then be able to store each meter as an individual item so it could still work, or does that feel cheap?
      singulars
      1. POComments/Suggestions on database design - Warehouse Stock Management
      1. USLuckyl337
    3. COCables could also be sold in fractions, like 1/4m. Of course you could create a row for each cm or mm, but it doesn't make sense. I've written several warehouse management systems, and I never felt the need to create a row for each piece of stock unless I have to track a serial number or something similar.
      singulars
      1. POComments/Suggestions on database design - Warehouse Stock Management
      1. USErich Kitzmueller
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload