If you're storing a key (say, a GUID) and a value (maybe a string), then all you'd need to do is make another field/column that handles timestamping. If you're

If you're storing a key (say, a GUID) and a value (maybe a string), then all you'd need to do is make another field/column that handles timestamping. If you're using an ORM like Hibernate, it will handle (most) of it automatically for you. Or, you could simply set your database up to use a composite key on the table (so the key becomes the key + revision number), though that isn't the best way since composite keys usually incur some performance overhead.