[db-wg] last-modified:, a succesor to changed:

On Thu, Apr 17, 2014 at 05:29:33PM +0200, Job Snijders wrote:
> On Thu, Apr 17, 2014 at 05:22:15PM +0200, Piotr Strzyzewski wrote:
> > On Thu, Apr 17, 2014 at 04:02:12PM +0200, Lutz Donnerhacke wrote:
> > > In iks.lists.ripe.db, you wrote:
> > > > not for others. So if it is kept as optional, those users who might 
> > > > prefer to clean the RIPE Database of many email addresses in possibly 
> > > > tens of thousands of objects will basically have to do it themselves.
> > > 
> > > How about a button in the LIR portal?
> > > "Remove all changed lines from all objects -i mnt-by"?
> > 
> > +1
> > 
> > Of course, this still leave us with some corner cases like person
> > objects without any maintainer.
> 
> I think this approach would be quite a clutch with no benefits. 
> 
> Aside from 'nostalgia' are there any operational reasons not to
> deprecate the "changed:" attribute? 

1. Breaking some scripts (already mentioned).
2. Some people keep real history of changes using this attribute. If
this is going to be deprecated, they would be forced to rewrite some
scripts.

> Keeping entirely redundant attributes for the sake of keeping them, 
> complicates database operations & usage. 

Piotr

-- 
gucio -> Piotr Strzyżewski
E-mail: Piotr.Strzyzewski at polsl.pl