when it comes to comments, to be able to enter different comments as time goes on, like why the price change. so a one to many would be nice to have. where the comments have their own dates.
Ashish Vijaywargiya sent the following on 8/6/2008 9:21 PM: > Hello Harmeet, > > I don't see any problem in adding this field. > Let's see what other has to say in one or two days. > > If nobody object on it then I will commit it soon. > > > On Thu, Aug 7, 2008 at 1:02 AM, Harmeet Bedi <[EMAIL PROTECTED]> wrote: > >> ProductPrice provide product to pricing information. It has tagging >> facilities through ProductPricePurpose and ProductPriceType. >> >> A problem we are facing is that we have customer requirements to store a >> comment with price. >> It seems like a general and useful thing. >> >> Attached is a diff on /applications/product/entitydef/entitymodel.xml that >> adds a single comment column to ProductPrice. Would you consider this patch >> or suggest some better way of adding a comment to ProductPrice information. >> >> thanks, >> Harmeet >> >> Index: entitymodel.xml >> =================================================================== >> --- entitymodel.xml (revision 2227) >> +++ entitymodel.xml (working copy) >> @@ -2109,6 +2109,7 @@ >> <prim-key field="currencyUomId"/> >> <prim-key field="productStoreGroupId"/> >> <prim-key field="fromDate"/> >> + <prim-key field="comment" type="comment"/> >> <relation type="one" fk-name="PROD_PRICE_PROD" >> rel-entity-name="Product"> >> <key-map field-name="productId"/> >> </relation> >> >> > >
