[Date Prev][Date Next] [Chronological] [Thread] [Top]

generalizedTimeOrderingMatch



Hello,

I use a attribute to give a time to live to some attributes in my ldap
server. (This attribute uses a syntax, a matching rule and an ordering rule
taken from createTimeStamp)

But when i try to search for old/new entries with this kind of filter :
(finValidite<20020528000000Z)
or
(finValidite>20020528000000Z)
i get some strange results :
- i get some entries without any 'finValidite' attribute !
- for both filters i get the same entries which are both newer and older !

> ldapsearch -b dc=upmc,dc=fr -x (finValidite>20020528000000Z)
<cut>
# 2000001, Standard, 92636261, D.E.S.S., IA, upmc, fr
dn: uid=2000001, cn=Standard, cn=92636261, cn=D.E.S.S., ou=IA, dc=upmc,
dc=fr
finValidite: 20010930000000Z

# 2000001, Personnes, upmc, fr
dn: uid=2000001, ou=Personnes, dc=upmc, dc=fr
finValidite: 20020110000000Z

# MODULE(S), IA, upmc, fr
dn: cn=MODULE(S), ou=IA, dc=upmc, dc=fr

# 92629001, MODULE(S), IA, upmc, fr
dn: cn=92629001, cn=MODULE(S), ou=IA, dc=upmc, dc=fr
</cut>

I think a do not use this objectclass correctly. Does someone have a valid
example ?

PS : the schema
attributeType ( 1.3.6.1.4.1.13129.1.2.1 NAME 'finValidite'
        EQUALITY generalizedTimeMatch
        ORDERING generalizedTimeOrderingMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 )

/*------------------------------*/
/*      Sebastien Bahloul       */
/*------------------------------*/
/*       Alca - Medasys         */
/*    http://www.medasys.fr     */
/* sebastien.bahloul@medasys.fr */
/*  Tél/Phone : +33 1 69337300  */
/*        Fax : +33 1 69337302  */
/*------------------------------*/