[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 ]
Sascha E. Pollok
sp+dbwg at iphh.net
Mon Jun 27 13:27:03 CEST 2022
Hi Janos. > Generally speaking it is a good idea to avoid using the comment character (#) in the > attribute fields (descr in this case), unless you use it for a comment indeed. > > In your example I have the impression that # is intended to stand for "number". it is indeed a "number" prefix but I am of course aware that in general everything behind a # comment sign could potentially get lost. @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. Thank you and best regards Sascha
- 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 ]