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] ***Error: Date in the future in changed: attribute '20070607'
- Previous message (by thread): [db-wg] ***Error: Date in the future in changed: attribute '20070607'
- Next message (by thread): [db-wg] ***Error: Date in the future in changed: attribute '20070607'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Thu Jun 7 16:25:15 CEST 2007
Marco Hogewoning wrote: [...] > > Regarding your other comment on backdating changes, keep in mind that a lot of > people actually keep a list of changed attributes in an object to have some > history of when people made changes. Which indeed is essential, as I was finding out recently. Loosing or removing old changed: lines really gets some pieces of software in the NCC mixed up. You'll only find out when applying for additional address space. At least the *oldest* one should always be preserved. > So you must be able to insert changed attributes with a date in the past. > Changing that would mean people have to find a new way to maintain history > or the database should get intelligent enough to copy history from the old > object before replacing it. > > MarcoH Wilfried.
- Previous message (by thread): [db-wg] ***Error: Date in the future in changed: attribute '20070607'
- Next message (by thread): [db-wg] ***Error: Date in the future in changed: attribute '20070607'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]