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] Suggestion: un-necessary error message

Previous message (by thread): [db-wg] Suggestion: un-necessary error message
Next message (by thread): [db-wg] Last Call: Proposal for Returning IRT objects

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

Niall O'Reilly Niall.oReilly at ucd.ie
Fri Jun 16 01:22:57 CEST 2006

On 15 Jun 2006, at 11:08, Denis Walker wrote:

> There are many simple errors like this the
> software can fix. But once we go down this road we run the risk of
> automatically fixing problems in a way that the user did not want.

I think there's room for a category of problems for which the software
would apply an automatic fix and give a warning.  The user could then
correct the problem if necessary.  This would be no more irritating than
the present practice of insisting that the robot knows better than what
the user specified, and forcing the user to fix a non-problem ... 8-)

For me, the ordering of the 'changed' attributes is a presentation
issue, not a semantic one.

/Niall

Previous message (by thread): [db-wg] Suggestion: un-necessary error message
Next message (by thread): [db-wg] Last Call: Proposal for Returning IRT objects

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

[ db-wg Archives ]