Module "decimal_precision" faulty by design
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Confirmed
|
Wishlist
|
OpenERP R&D Addons Team 3 |
Bug Description
There are several design faults with "decimal_precision" module.
Quote from module description:
-------
This module allows to configure the price accuracy you need for different kind
of usage: accounting, sales, purchases, ...
The decimal precision is configured per company.
-------
Fault #1:
Although it states that there is an option to set decimal precision per company, the model "decimal.precision" has no company field. It is the same when you observe the functionality in use by several other modules, like accounting, because it initializes the classes per database, not per company (IMHO it is impossible), evidently the functionality stated in the description is not being performed.
Fault #2:
When we see the float field definition there is such thing as 2 parameters - the number before decimal separator and the number after, still the model "decimal.precision" has only one field - digits.
Fault #3:
Normally you should not use language specific capitalized strings with spaces inside as codes for matching the particular setting, still there is "Sale Price", "Purchase Price", "Account", "Stock Weight", "Product UoM", "Shipping Delay". Which is amateurish coding style. This is not according to conventions in the other places with OpenERP, for example with properties, where you can observe completely opposite situation, for example - "property_
Hello,
I am confirming the issue raised in Fault #1 as wishlist, because we do not have such functionality in current version.
In response to Fault #2 and #3, we have given the digits field for only precision that is number of digits after decimal separator. So it is working good and as per need. While you can give the string as per your need. In the end it will be evaluated in the query as %s.
Thanks for your participation.