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/db-wg@ripe.net/

[db-wg] changed-lines in objects.

Previous message (by thread): [db-wg] changed-lines in objects.
Next message (by thread): [db-wg] changed-lines in objects.

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Mark Prior mrp at mrp.net
Sat May 24 13:38:44 CEST 2003

At 12:44 PM +0200 24/5/03, Shane Kerr wrote:
>It does not address the problem that people assume that the "changed:"
>attribute actually properly identifies when an object was changed.  If
>this is desired, then the attribute should be made mandatory, and the
>timestamp always added by the server.  In the past, there has been
>opposition to this idea.
>
Your suggestion does have merit. If people want to tag the changed 
line they can do and for those of us who don't we just see when it 
was (possibly) last changed.

Why did people oppose the idea of it being added by the server?

Mark.

Previous message (by thread): [db-wg] changed-lines in objects.
Next message (by thread): [db-wg] changed-lines in objects.

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]