Timeline for Database Design for Inventory
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16, 2015 at 19:43 | vote | accept | Berry Bonds 3 | ||
| Apr 15, 2015 at 12:34 | history | edited | Tulains Córdova | retagging | |
| Apr 14, 2015 at 19:02 | answer | added | ChuckCottrill | timeline score: 1 | |
| Apr 14, 2015 at 3:24 | comment | added | user40980 | The reason I ask this is that its one thing to have a bunch of specific clothing related details if you are, say, a clothing store. On the other hand, if you are a general retailer, that level of detail of clothing fields isn't going to be applicable to the toy department, or home improvement, or automotive, or ... And thus you will want a more general solution across the board. But it would help to understand the nature of the product areas and range of items to be added. | |
| Apr 14, 2015 at 3:05 | answer | added | Robert Munn | timeline score: 9 | |
| Apr 14, 2015 at 1:23 | comment | added | h.j.k. | I would imagine sizing information is different for jeans, t-shirts and dresses too... | |
| Apr 13, 2015 at 21:07 | history | edited | user40980 | CC BY-SA 3.0 | Bulleted lists for types and attributes. Remove 'thanks'. |
| Apr 13, 2015 at 21:06 | comment | added | user40980 | How many 'specific attributes' do you have? Is it an entirely known list? or are you going to get odd ball ones in there from time to time as new products are added? | |
| Apr 13, 2015 at 21:06 | review | First posts | |||
| Apr 13, 2015 at 21:23 | |||||
| Apr 13, 2015 at 21:05 | history | asked | Berry Bonds 3 | CC BY-SA 3.0 |