[db-wg] Whois changes
- Previous message (by thread): [db-wg] Whois changes
- Next message (by thread): [db-wg] Whois changes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at ripe.net
Wed May 11 10:13:31 CEST 2005
Erics wrote: >Hi, > >i think this is a good idea. >The default output should show the last changed date. >This could be very helpful for LIRs. > > It is easy for users who need this information to get it -- add the "-B" flag to your query. Also, most users of the database are not LIRs. Relying on the "changed:" attribute to know when objects were updated has the problem that there is no error checking on it. A user can put almost any "changed:" value that they want. I could update my person object today to have this value: changed: ripe-dbm at ripe.net 19901215 I think in the past people have suggested a "reliable" timestamp on objects in the database, but other people have argued against it. One suggestion was to add an optional attribute with a reliable timestamp that would get generated by the database. This way, if it is there you can trust it, but if it is not then you must rely on "changed:" attributes or do without any information. -- Shane
- Previous message (by thread): [db-wg] Whois changes
- Next message (by thread): [db-wg] Whois changes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]