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]/
another lookup problem
- Previous message (by thread): another lookup problem
- Next message (by thread): another lookup problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David R. Conrad
davidc at apnic.net
Fri Jul 19 05:51:38 CEST 1996
Hi, As APNIC uses the RIPE database software, I thought I might intrude here for a second and throw in my two yen. >> Names likes this will be rejected in the next release of the updating >> code. Names should consist of at least two parts, not counting >> abbreviated parts/titles. As I have mentioned in the past, there are people who have only one name. If you decide to do this, please make a compile or run-time configuration option that will defeat this syntax check. > WRT "fuzzy" / wildcard matches - it would make the RIPE-DB software > more user friendly (and maybe more attractive for deployment by other > registries) to provide for (implicit/explicit) regexp or partial key > matches. To what end? Is the purpose of the database registration information lookup or a more general white pages service? I' would suggest the former and leave the latter to the WHOIS++/LDAP/X.500 crowd. Regards, -drc
- Previous message (by thread): another lookup problem
- Next message (by thread): another lookup problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]