Add field related historical in ORM

Registered by Christophe CHAUVET

Add new fields, a related historical (eg: on product to replace list_price and standard price)
Why replace float by historical, because my price can change the next month, or which price price for a specific date.

The date to define has been passed by the context.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Christophe CHAUVET
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
Accepted for trunk
Implementation:
Started
Milestone target:
milestone icon 6.0
Started by
Christophe CHAUVET
Completed by
Christophe CHAUVET

Related branches

Sprints

Whiteboard

I made a module: historical_data as an example in trunk-addons-community branch
Here is more info from the __terp__.py file:

This module is a proof of concept on how to use historical data in Open ERP and
how you can easily inherit fields to create new type of fields. This module
shows two approaches to manage historical data. It based on an insurance
company need that manages contracts that evolves in the time. When a case is
opened, the information seen on the case should be the one of the contract
at that time.
  * Contracts have versions valid in the time. Data are in versions of contract,
    but displayed on the contract using a special fields.related_history. (an
    expression based on the date is passed on the context) If you open a contract
    from a case, the information you will see depends on the date of the case.
    If you open contracts from the menu, the information displayed depends on the
    current date.
  * Partners management is based on the audittrail module. When you open
    a partner from a contract, you will see the name of this partner related
    to the date of the contract. Don't forget to activate a rule on res.partner
    in the audittrail module to test this.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.