Proposal for solving price_accuracy

Demos are available in English, German and French (not completely translated) here
 http://www.chricar.at/ChriCar/OpenERP.html

Currently the price_accuracy is defined as startup parameter of the server process
* all databases connecting to this server process get n digit prices etc whatever is defined as price_accuracy at startup
* all products will have prices with "price_accuracy" decimal digits, which looks ridiculous for products which are sold at some 1000€
* database tables are not altered, hence entering something like 1,1111 will result in 11,1100 - except altering the db tables manually
IMHO this "solution" does not meet business needs

Proposal:
the "price accuracy" has to be defined at product level as price_unit.
* per unit
* per 100 units
* per 1000 units and so on
- this would allow to stick to decimal(16,2) definitions in the database
- add ONE field to products view - default price_unit=1
- run only ONE server process
- display the price as
11,11
11,11%
11,11%0
- use standard_price/price_unit internally to calculate various values
IIRC qty*standard_price/price_unit will give a decimal(16,2) target field (if defined so) - exactly what is needed

this should be fairly easy to implement and become part of the standard

BTW using different UOM etc is not appropriate - Example
Purchase of gasoline / diesel -
qty in liter = 1500
price is quoted with 3 or 4 digits 1,1234
OpenERP should quote 112.34%

alternate approach
price in Cents