0003433: Keep update versions of every entry in the database

Description

In my opinion it would be great to give support to a client. Having different versions of every record would give you all the information among the time of an entry. Which changes where made in that entry, who made them... Every version of the same record should have "active" column, to show which one of those versions is actually working.
For example, a product, could have some updates in its name, associated bpartner, unit of measure... keeping all these changes recorded with this version utility would help hugely the auditory and supporting activity.

Tags

ReleaseCandidate

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

has duplicate	feature request	0004619		closed	pjuvara	Method to log all changes to the database without generating log files
related to	feature request	0003432		closed	iciordia	Possibility to have access to deleted data

Notes
(0007022) user71 2005-06-01 00:00 edited on: 2008-06-12 09:44	This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1853844 [^]

Issue History
Date Modified	Username	Field	Change
2008-07-01 18:31	pjuvara	Tag Attached: ReleaseCandidate
2008-07-01 18:32	pjuvara	Status	new => acknowledged
2008-07-01 18:32	pjuvara	Relationship added	related to 0003432
2008-11-16 07:44	pjuvara	Assigned To	user71 => pjuvara
2008-11-16 18:41	pjuvara	Relationship added	has duplicate 0004619
2009-05-22 19:36	pjuvara	Assigned To	pjuvara => iciordia
2010-03-08 16:50	pjuvara	Status	acknowledged => scheduled
2010-03-08 16:50	pjuvara	fix_in_branch	=> pi
2010-03-08 16:50	pjuvara	Status	scheduled => resolved
2010-03-08 16:50	pjuvara	Fixed in Version	=> 2.50MP12
2010-03-08 16:50	pjuvara	Fixed in SCM revision	=> NA
2010-03-08 16:50	pjuvara	Resolution	open => fixed
2010-03-08 16:50	pjuvara	Status	resolved => closed