best practice for "changed:" field
Shane Kerr shane at time-travellers.org
Mon Dec 5 18:06:16 CET 2011
Martin, On Mon, 2011-12-05 at 18:01 +0200, Martin T wrote: > As I understand, in RIPE database every object has a mandatory > "changed" field. There can be multiple "changed" fields. Is it a good > practice to keep all the changes made to the object? What are the > advantages and disadvantages? The "changed:" attribute is for your own purposes, as I understand it. So, if you don't care about the history of changes, then you can keep only a single "changed:" line. If you want a full history, then you can add a new "changed:" line with every update. The drawback here is that you can end up with a very big object, of course. And of course you can remove some changes based on whatever rule you want; for example if you don't care about changes more than a year old, or only want to keep the last 5 changes. -- Shane
[ db-help Archives ]