Hi, I dont think there is any documentation at all about this feature.
When you add _history it creates a new table with model_name + __history and whenever the record is updated (create, write) a copy of the same is stored into the __history table. If you read with _datetime specified in the context, then the record returned will be the record from history table as it was on that time instead of current one in the master table. Also see the IRC logs of last few days as we have been discussing the history features with students of GSOC. On Fri, Apr 8, 2011 at 10:47 AM, Paul J Stevens <p...@nfg.nl> wrote: > > Hi all, > > What is the usage envisioned for the _history model? > > I'm building the support ticket system as designed by Cédric and > Sharoon, but I can't find out how to access the history. Do I need to > write manual accessors? > > The only examples I can find that do stuff like this are > sale_opportunity and ir.request, but they seem to do their own > implementation of historization. > > So what is the purpose of this attribute? > > Any pointers to documentation, examples or use-cases appreciated. > > thanks. > > -- > ________________________________________________________________ > Paul Stevens paul at nfg.nl > NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 > The Netherlands________________________________http://www.nfg.nl > > -- > tryton-dev@googlegroups.com mailing list > -- Sharoon Thomas Business Analyst & Open Source ERP Consultant CEO @ http://openlabs.co.in -- tryton-dev@googlegroups.com mailing list
