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]/
** URGENT ** New database software at the NCC
- Previous message (by thread): ** URGENT ** New database software at the NCC
- Next message (by thread): FYI: InterNIC/MERIT/RIPE database exchange format
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
woeber at cc.univie.ac.at
Wed Sep 8 12:29:37 CEST 1993
Marten, >Just some explanation, the messages sent to assign are first checked to see >if they are already in the database, and currently bounced back to the NCC if >they are. I think what I will do is create something like auto-assign, which >has the same "on-the-fly" features as auto-dbm, but will only ADD new >objects, and bounce all objects that are already present. This would mean >that also contact people that are already present will not be updated when >sent to auto-assign. ...does this mean that we are no longer able to submit *updates* for person objects along with a new network object from the 193,194 address range? If this is the case, then I think we should generally go for a system where *all* objects *with the exception of objects for newly assigned networks* should go to the ripe-dbm mailbox. Wilfried.
- Previous message (by thread): ** URGENT ** New database software at the NCC
- Next message (by thread): FYI: InterNIC/MERIT/RIPE database exchange format
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]