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/
problems with data base updates
- Previous message (by thread): Possible addition tag for the aut-sys object.
- Next message (by thread): zone-c not mandatory
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marten Terpstra
Marten.Terpstra at ripe.net
Fri Feb 19 15:07:21 CET 1993
rv at deins.informatik.uni-dortmund.de writes: * Hello, * * recently I mentioned to Daniel on the phone, that it looks like some * "connect:" fields are filtered (without warning) in the RIPE data base. * I just came across an example (I will keep looking), the record for * network 139.1: I'm very sorry to say that this is all my fault, and it was even worse than some "connect:" fields dissapearing ... In fact what happened is that all LOCAL connect fields dissapeared from the database because of an(other) error in the procedure that adds the routing tags to the database. I have done the following to correct this: - modified the script that adds the routing tags to leave the connect fields in, - rebuild the database, and added a "connect: LOCAL" field to any network that had no connect tag in the current database. I have checked this extensively and are sure that ONLY "connect: LOCAL" fields dissapeared. All other connect fields were not removed, and still have their old value. My apologies for this error. If you do find any inconsistencies, please inform us, and we will process with the highest priority. -Marten
- Previous message (by thread): Possible addition tag for the aut-sys object.
- Next message (by thread): zone-c not mandatory
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]