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] Updating Descr part of object with # results in No Operation

Previous message (by thread): [db-wg] 2022-01 V2 Resource Holders Address
Next message (by thread): [db-wg] Updating Descr part of object with # results in No Operation

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

Sascha E. Pollok sp+dbwg at iphh.net
Tue Jun 21 10:11:58 CEST 2022

Hi everyone,

I just tripped over something today which I have never noticed after >20 years of using 
the RIPE DB :-) It might be explained somewhere but I haven't found anything so here it is.

I am updating an inetnum object from:

  descr: Testobject Ticket #12345
to
  descr: Testobject Ticket #123456

using Syncupdate. This results in a "No Operation" (Warning: Submitted object identical to 
database object). Is this intentional? It works if I remove the # and add it again in a 
second step. I assume it's something about it being interpreted as a comment but even if 
that's the case, I should still be able to update it.

Can someone enlighten me?

Thank you and best regards
Sascha

Previous message (by thread): [db-wg] 2022-01 V2 Resource Holders Address
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 ]