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]/
Modifying references to contact info in the RIPE DB
- Previous message (by thread): Modifying references to contact info in the RIPE DB
- Next message (by thread): Modifying references to contact info in the RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joao Luis Silva Damas
joao at ripe.net
Thu Jun 24 11:04:40 CEST 1999
Bernard Steiner <bs at eunet.ch> writes: * * > That the original person referenced got deleted some time in the past and * a new one with the same name was introduced into the database. * * Coming to think about it... * How about catching such (obvious) cases where the first changed date of the * person is younger or either of the changed dates is not available ? * How much human intelligence would that require to sort out ? As a philosopher said some time ago: "I am me and my circumstances". This also applies to the RIPE Database (and in a very big measure). I guess everyone remembers the (in)famous -c changes and how many changed lines (particularly the old ones) disappeared during that period. We can do the check you propose and see how many objects would not get modified. If it happens to be a small number we can look at them individually. If not it is back to square one. Thanks for the suggestion, Joao * * Bernard * *
- Previous message (by thread): Modifying references to contact info in the RIPE DB
- Next message (by thread): Modifying references to contact info in the RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]