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] Proposal - Maintaining person, role and domain objects
- Previous message (by thread): [db-wg] Proposal - Maintaining person, role and domain objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Wed Jul 11 09:20:28 CEST 2007
Denis Walker wrote: [...] >>1) >>This sentence, and the explanation that follows, implies that exactly >>*two* objects are required here and supported. It should work, even >>for the cases where admin-c: and tech-c: are (to be) different. Just >>double-checking. >> > > > Not quite right. My view is that these two mutually referencing objects > must be the FIRST two in an update message. There can be other objects > in the message also, but unrelated to this 'startup procedure'. > > To avoid over complicating the code we want to keep it simple and only > have 2 objects with the mutual reference for the new creation. If you > want a different admin-c and tech-c in the new mntner, none of which > currently exist, first create the new mntner/person pair using the one > person as both admin-c and tech-c. Then create the second person and > modify the mntner. Yep, that's how I read it, too. And I agree. But it should be made explicit in any documentation that goes with this, that for this case an additional step is necessary. No big deal... Wilfried.
- Previous message (by thread): [db-wg] Proposal - Maintaining person, role and domain objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]