Forum: Database Design Jun 19th, 2007 |
| Replies: 8 Views: 5,641 There are cases when there are different ways to normalize. This is related to my question 1 in the first message.
For example, we have a simple inventory database tracking the quantities that go... |
Forum: Database Design Jun 12th, 2007 |
| Replies: 8 Views: 5,641 Another good example would be an inventory system. All types of transactions will end up to an IN and an OUT to your inventory. So, all sales, purchases, adjustment, issuance--although they may have... |
Forum: Database Design Jun 12th, 2007 |
| Replies: 8 Views: 5,641 So, do you mean that you are against fields like "type". Like example, for sales, you have a "type" field that identifies if it is take-out or dine-in or for delivery. And if it is for delivery, you... |
Forum: Database Design Jun 12th, 2007 |
| Replies: 8 Views: 5,641 There are some things that I am in a dilemna with about general database/table design issues. Each has its pros and cons. What do you think are the best practices? Here are some problems.
1. You... |
Forum: Database Design Jul 25th, 2006 |
| Replies: 1 Views: 10,544 Hello. I am a software engineer and I am trying to design a database for an inventory module. I have a problem about the application of the costing methods (e.g. Standard/FIFO/LIFO/Average/etc.).
... |