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] Updating Descr part of object with # results in No Operation
- Previous message (by thread): [db-wg] Updating Descr part of object with # results in No Operation
- Next message (by thread): [db-wg] Updating Descr part of object with # results in No Operation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Tue Jun 28 17:13:13 CEST 2022
Hi Gert, > On 28 Jun 2022, at 08:31, Gert Doering <gert at space.net> wrote: > > Hi, > > On Mon, Jun 27, 2022 at 01:47:23PM +0200, Edward Shryane via db-wg wrote: >> The comparison logic ignores comments as it's not considered part of an attribute's value, i.e. it's not significant (it's only for humans to read as metadata). > > I find that approach flawed. If I send you an update that differs in > parts humans will find interesting to read, and that you are going to > *store*, ignoring it as part of the "has anything changed" check will > do no good, and create friction at times. > > Ignoring bits that are *not stored* (like, whitespace normalizations, > or possible uppercase/lowercase stuff on attribute names, etc.) makes > sense to me. Emphasis on "not stored". > The DB team will investigate the impact and complexity of making this change in Whois update. If there are no objections we can plan to include it in the next release. Regards Ed Shryane RIPE NCC
- Previous message (by thread): [db-wg] Updating Descr part of object with # results in No Operation
- Next message (by thread): [db-wg] Updating Descr part of object with # results in No Operation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]