we'll compare with an arbitrary precision, untill we have a good way of
specifying this.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30065 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30064 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Update titles for milestone report

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30063 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30062 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30061 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30060 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30059 20353a03-c40f-0410-a6d1-a30d3c3de9de

This is required to customize an OOoChart depending of values entered in a
dialog form.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30058 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30057 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30055 20353a03-c40f-0410-a6d1-a30d3c3de9de

Use a default namespace to retrieve the Status


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30054 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Make the report working even if stop dates are not defined everywhere

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30053 20353a03-c40f-0410-a6d1-a30d3c3de9de

 To keep the backward compatibility with the persistent objects which were not updated yet (ie.: Inside old business templates), it was added the some imports from PortalTransforms.

 Without this patch the persistent objects becomes broken and not accessible or updatable by Subversion and cause problems to update erp5_core.


 XXX Please remove this path once portal_transforms is not used or once all objects are already moved to latest versions of ERP5 (after transforms be moved at least).



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30052 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30051 20353a03-c40f-0410-a6d1-a30d3c3de9de

* add missing import of Query

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30045 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Allows to select the state of project when call the milestone report

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30044 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30043 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30042 20353a03-c40f-0410-a6d1-a30d3c3de9de

* update docstring
* remove useless logs

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30041 20353a03-c40f-0410-a6d1-a30d3c3de9de

the default value for multiple list fields should be [] not None. since r29556, ('', '') item will be selected if the default value is None.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30040 20353a03-c40f-0410-a6d1-a30d3c3de9de

Add one more select_dict case: when there is no direct hint given, but the query implicitely favors a table over the other.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30039 20353a03-c40f-0410-a6d1-a30d3c3de9de

- add a column which mapping is ambiguous (could happen on 2 tables)
- add a utility method to generate SQLExpression instances from parameters


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30038 20353a03-c40f-0410-a6d1-a30d3c3de9de

Cleanup "items" in that relation field instance. It was not allowing to choose between multiple ambigous results

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30037 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30036 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30035 20353a03-c40f-0410-a6d1-a30d3c3de9de

Also fix a typo (missing colon at end of method definition).


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30034 20353a03-c40f-0410-a6d1-a30d3c3de9de

Split buildSQLQuery into 2 parts: one responsible for building the EntireQuery (and responsible for parameter backward compatibility), and a second to just render that EntireQuery as a dict. This will help testing EntireQuery.
Update interface accordingly.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30033 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30032 20353a03-c40f-0410-a6d1-a30d3c3de9de

of ERP5


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30031 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Add new report in order to have global overview of milestones

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30030 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30029 20353a03-c40f-0410-a6d1-a30d3c3de9de

- specify in IMetadataDiscoverable.getContentInformation that the return type
  is a dictionnary


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30028 20353a03-c40f-0410-a6d1-a30d3c3de9de

here, x[0] is a Products.ERP5Type.Message.Message object, so we need to sort by str(x[0]) otherwise the sort result is unexpectable.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30027 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30026 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30024 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30023 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30022 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30021 20353a03-c40f-0410-a6d1-a30d3c3de9de

Until now, when using, for example, VAT, you put like this:

price=0.196, efficiency=1.0

so the result by getAggregatedAmountList is, if the base is 100:

price=0.196, efficiency=1.0, quantity=100

Thus, the total price is 19.6.

This works but not compatible with rounding, as, for instance, if we want to 
round it up to 20, the result is not saved at anywhere.

So, from now on, we do like this instead:

price=1.0, efficiency=0.196

so the result is:

price=1.0, efficiency=0.196, quantity=100, total price=19.6

The total price does not change. When we apply a rounding method, it would 
result in:

price=1.0, efficiency=0.196, quantity=100, total price=20

--

This modification is approved by YO and Yusei.

TODO: write some test-cases



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30019 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Change the usage of
price, quantity and efficiency in Trade Model Line

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30018 20353a03-c40f-0410-a6d1-a30d3c3de9de