Hi Sascha, This is intentional behaviour, any comment is not considered part of the attribute value. If you only update a comment, the object is considered to be identical to what it was before (i.e. there has been no significant change). The workaround as you mentioned is to change something else at the same time. Regards Ed Shryane RIPE NCC
On 21 Jun 2022, at 10:11, Sascha E. Pollok via db-wg <db-wg@ripe.net> wrote:
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
--
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg