This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] last-modified:, a succesor to changed:
- Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] last-modified:, a succesor to changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Thu Apr 17 17:29:33 CEST 2014
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? Keeping entirely redundant attributes for the sake of keeping them, complicates database operations & usage. Kind regards, Job
- Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] last-modified:, a succesor to changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]