What are some design patterns for doing version control of an object?

Question

What are some design patterns for keeping a history of an object as it changes. I don't need anything as heavy duty as event sourcing, just the ability to save past versions when a specific event happens (in this case when a print form button is pressed).

score 7 · Accepted Answer · answered Feb 24 '09 at 20:05

7

You could look for the memento pattern

answered Feb 24 '09 at 20:05

Melursus

10,328
19
69
103

score 2 · Answer 2 · answered Feb 24 '09 at 20:06

2

This sounds isomorphic to tracking undo information. The usual pattern for this is a variant of the Command pattern: you keep a queue in time order of previous states, with an operation to restore to the previous state.

answered Feb 24 '09 at 20:06

Charlie Martin

110,348
25
193
263

The difference is that the history itself is persisted whereas with undo info you don't need anything of the sort. – George Mauer Feb 24 '09 at 20:15

score 1 · Answer 3 · edited Sep 02 '13 at 15:21

1

I suggest you have a look at Martin Fowler's temporal patterns: http://www.martinfowler.com/eaaDev/timeNarrative.html

edited Sep 02 '13 at 15:21

answered Sep 02 '13 at 14:54

charlb

1,076
9
18

What are some design patterns for doing version control of an object?

3 Answers3