[db-wg] Updating Descr part of object with # results in No Operation

Hi Sascha,

> On 27 Jun 2022, at 13:27, Sascha E. Pollok <sp+dbwg at iphh.net> wrote:
> 
> ...
> @Ed: If this were a comment (it is not here but what was I thinking to use the # for anything else :-D) wouldn't this still be something someone could want to update? Let's say a peer's name in an aut-num object or similar? I would have expected that also comments should get the chance to be updated.
> 
> Not a big issue of course but still wondering why it was implemented that way.
> 

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).

Because of that, if only a comment has changed in an update the object itself is considered identical and a NOOP is returned.

Regards
Ed Shryane
RIPE NCC