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/
Inverse Query Failures
- Previous message (by thread): An AUP for the RIPE DB ?!
- Next message (by thread): New Document available: RIPE-153
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
Daniel.Karrenberg at ripe.net
Fri Jan 17 17:40:36 CET 1997
I was asked to look into invers queries going wrong in order to determine which additional indices might be useful. I looked at 5245997 recent queries 6236 (0.11%) of which were reverse. Of these 1428 (24.72%) failed because no match could be found and 461 (7.39%) failed because either no attribute name was given or an attribute name which does not have an inverse index was given. Unfortunately no more details are logged about the latter type of failures. We will change that a.s.a.p. and report back if there are signigficant findings. I have looked at the data that was logged and could detect no clear trends pointing to the need for additional indices. Daniel
- Previous message (by thread): An AUP for the RIPE DB ?!
- Next message (by thread): New Document available: RIPE-153
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]