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/db-wg@ripe.net/
"changed" field should be deleted
- Previous message (by thread): "changed" field should be deleted
- Next message (by thread): "changed" field should be deleted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joe Abley
jabley at clear.co.nz
Fri Jun 5 16:39:58 CEST 1998
On Sat, 6 Jun 1998, Joe Abley wrote: > Perhaps the displayed/retrieved version of the "changed" field should > include a message-id instead of the e-mail address? These are supposed to > be unique, and usually contain a hostname/FQDN that is probably sufficient > to identify the updater. > > I am assuming that the vast majority of people make updates using > e-mail... Actually, thinking about it, why is the changed field "id" an e-mail address at all? Given that most (all?) records are protected to some degree by maintainer fields, surely anything good enough to identify the changer to his fellow maintainers would do? A quick fix might be to expunge all text immediately following the "@" in the changed fields of current records? Or perhaps simply return the records in response to queries with the changed fields munged in a similar way? Joe -- Joe Abley <jabley at clear.co.nz> Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/
- Previous message (by thread): "changed" field should be deleted
- Next message (by thread): "changed" field should be deleted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]