[db-wg] Suggestion of change for inverse query of notify
- Previous message (by thread): [db-wg] Suggestion of change for inverse query of notify
- Next message (by thread): [db-wg] Proposal: DB object syntax change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Wed Mar 19 17:54:41 CET 2014
Hi Denis, Denis Walker wrote: [...] > So for your specific examples, the inverse query looks for objects with > "notify: info at resilans.se". This includes the INETNUM but not the ROUTE > object. my apologies for getting off-track in my previous mail. I was -again- bitten by the deault filtering, silently "eating" the notify: line in the inetnum object that was quoted :-( And I didn't "go to the source". Lesson learned. Sorry, Wilfried > The other query looks for address space including the address 194.14.3.0 > and any matching ROUTE object. So you get back both the INETNUM and > ROUTE object. > > Regards > Denis Walker > Business Analyst > RIPE NCC Database Team
- Previous message (by thread): [db-wg] Suggestion of change for inverse query of notify
- Next message (by thread): [db-wg] Proposal: DB object syntax change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]