On Thursday, 27 February 2014 08:06:51 UTC, Erland Sommarskog  wrote:   
   > All this depends on business rules, but yes, I would   
   > expect a price column in a Orderline table. That gives   
   > the price for that specific order. The customer may have   
   > gotten a discount. And more importantly, if you change   
   > the price for the product, you don't want that to affect   
   > old orders.   
   >   
   > Although, in your example I would store 10 in the Price column   
   > in the Orderline table. If it was called Amount I would   
   > store 30.  But that's more of a language issue.   
      
   The discount may be volume-dependent and also not a unit   
   price; for instance, oranges, $0.50 each, or 3 for $1.00.   
      
   Another way to write that is: item, 3 oranges; number, 1.   
      
   Maybe you need to hold the user ID that input or edited   
   the order line, in case one customer is getting too much   
   discount.   
      
   And a belated thought - well, two thoughts; one is that   
   we may be doing too much of Tony's college homework;   
   another is that pricing is more important on the invoice   
   than on the order.  Or maybe that's a language issue too...   
      
   Also, several stories on the "Not Always Right" and   
   "Not Always Working" web sites are coming to mind.   
   e.g.    
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)