Re: [db-wg] ***Error: Date in the future in changed: attribute '20070607'

[Marco Hogewoning <]

On Thu, Jun 07, 2007 at 01:17:47PM +0100, Jeroen Massar wrote:
> >> As Max pointed out, unless dates in the RIPE db all have to be in UTC,
> >> in his time zone it was already that date as his clock is 2 hours ahead
> >> of GMT which is 3 hours ahead of UTC at the moment.
> > 
> > Another option would be to omit the date/time in the changed: and
> > have the DB software add in what it thinks is the "appropriate" $now.
> 
> Would be fine with me. Especially as 'backdated' updates can't then be
> made anymore. The changed line then really reflects exactly that: when
> it was changed.

Jeroen,

The feature is already there, if you insert a changed line without a date it
will already be added:

| ---
| Modify SUCCEEDED: [aut-num] AS5417
| ***Warning: Date '20070508' added to changed: attribute 'marcoh@localhost

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.

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

Attachment: signature.asc
Description: Digital signature