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]/
"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 ]
Michael van Elst
mlelstv at xlink.net
Fri Jun 5 16:25:59 CEST 1998
On Fri, Jun 05, 1998 at 03:18:28PM +0200, Daniel Karrenberg wrote: > > I agree that this needs attention. > The whole changed: functionality should be reviewed. > > I agree that a short term measure could be to suppress changed > information unless explicitly requested. This would also allow > us to check the whois query logs for those requesting it ...;-). > Does anyone know if this would break any knows scripts or uses > of the database? > > Daniel Hiding the changed: lines definitely breaks every system that keeps _copies_ of the entries because it is impossible to update entries from these copies without trashing the existing entries. And if you make the changed: line availables optionally then those who want to use addresses will quickly figure out how to get them. Greetings, -- i.A. Michael van Elst / phone: +49 721 6635 330 Xlink - Network Information Centre \/ fax: +49 721 6635 349 Vincenz-Priessnitz-Str. 3 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster at xlink.net [ Xlink Internet Consulting GmbH, Sitz Koeln ] [ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert ]
- 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 ]