Comment 4 for bug 800970

Hello,

@RD Framework:
I have checked again this issue and you are right "osv.osv_memory does not handle properly digits_compute argument". I have applied the patch on this http://bazaar.launchpad.net/~openerp-dev/openobject-addons/trunk-bug-788064-mma/revision/4765 revision and create a new db It is working fine But the problem creates when I am restarting the server, then osv_memory can't handle digits_compute So this is the generalizes issue for all osv_memory.That's why I am also affect this issue to server and confirming this issue on server side

@RD Addons2:
Now about your case #1 you have talked about the qty field on partial picking wizard, and this is is also confirm I would like to suggest here to use a "Stock Weight" 's decimal accuracy on qty field of the partial picking wizard.
That's why I am confirming your case#1 on addons side.

According to your "Average price (cost price)" related issue which is already post on lp:788064 and after this bug 's fixes on server side it will solved and I am also related that bug to this one.

@Graeme:
Thanks for your reply!
Now I would to like giving the answer of your question regarding your comment#3 "why should it be Purchase Price?"
Ans : Because the cost price is always related with the purchase order or purcahse price. In partial picking wizard the float field "Cost" is coming only when your recepation is incoming, means your picking is gerenared from the PO and also you have select the "Average price" in porduct form. So this field does not related to sale or sale price.
That's why here using "Purchase Price" 's decimal accuracy.

Now let 's disuss about your first point which is "use the same precision for all unit prices".
This point is a "Wishlist" so would you please post new bug report on this and if you allow me then I will post.
Because your this point needs a more improvement and discussion So I am consider this as a "Wishlist".

Hope you will agree with me and correct me if I am wrong on this.

Thanks.