In the report pos order, average_price was set as a numeric(16,2), therefore, if the amount was too big, it led to a psql crash:
A field with precision 16, scale 2 must round to an absolute value less than 10^14.
This reverts commit 97d097a2af.
As explained in the commit comments (on Github), this patch leads to an infinite loop in 7.0, the filter of the pos orders report using the '=' operator in its domain, which is not available for datetime fields, but is for date fields.
This should not be forward ported to newer release (saas-3)
product_id column of pos_order_line is a product_product
the left join of l.product_id was done on product_template, instead of product_product
It worked as long as the ids product_product were the same as product_template. Meaning that, if you used variants, this report view was screwed.
The date_order field of the pos.order is a datetime, not a date
As, in report.pos.order, the date field is related to date_order of the pos.order
We usually do not commit fixes altering the model fields structure in 7.0, but this one is retro-compatible, as the database structure won't change
- refactorisation of the code: 2000 lines of code removed
- fixed all the bugs
- support for tax included/excluded prices
- fixed rounding troubles
- don't print the ticket if partial payment
- cleaning features:
- workflow reviewed: New -> Done -> Posted / Invoiced
- generation of journal entries/invoice is now correct
- only one picking per PoS order
- wizard to apply global discount (on each lines)
- useability:
- reviewed the main point_of_sale screen
- statements are open by default
- removed non-useful features
- advances (you use a special product for this)
- contracts numbers
- refund with exchange (you just create a new sale with negatives qty)
- removed validation steps
- scan product wizard
- clean and complete YAML tests (work in progress)
bzr revid: fp@tinyerp.com-20110925140930-s6zibvn51k3914in
Denis Ledoux
Vo Minh Thu
Amit Patel
Saurang Suthar (OpenERP)
Fabien Pinckaers
ARA (OpenERP)