VLV indices and multi-value attributes

["Eric C. Hagberg" <hagberg@ms.com>]

If this topic has been discussed to death, please excuse my ignorance,
however I'm wondering what "draft-ietf-ldapext-ldapv3-vlv-01.txt" and "draft-ietf-ldapext-c-api-vlv-01.txt"
should or shouldn't say with respect to what should be done when an LDAP
server (supporting the vlv control) creates a vlv index for an attribute,
especially with respect to how it should handle a multi-valued attribute.

For example, the server we're using to query has a database containing some records which have more than one last name. If we create a vlv index, only the first (or last?) attribute value is placed in the index. This creates an apparent lack of data if you display a page of results which doesn't contain the "missing" (non-indexed) attibute value, which would not be missing if you did a similar "normal" substring query on the sn attribute.

So, I would think that it would make sense to have multiple-valued attributes vlv-indexed for each value, rather than just arbitrarily throwing away one (or more) of the values when creating the index.

Perhaps the indexing of all the values should be mandatory, while the display of those repeated attributes (which would be returned as though they were individual records in the database) could be handled through another option to the vlv query?

Does this make sense?

Thanks,
-Eric
 
 
 

begin:vcard
adr;dom:;;;750/11
adr:;;750 Seventh Ave.;New York;NY;10019;USA
n:Hagberg;Eric
tel;fax:1212-762-1011
tel;work:212-762-2558
x-mozilla-html:FALSE
org:Morgan Stanley Dean Witter;IT
version:2.1
email;internet:hagberg@ms.com
fn:Eric C Hagberg
end:vcard