hi, i am currently working on changing modification layer to use txn services and have a few questions about dropaliasindices:
*is it true that an entry has object class ALIAS_OC iff it contains attribute ALIASED_OBJECT_NAME_AT. *where can I check the ldap definitions of atttributes given in SchemaConstants. I wanted check if ALIASED_OBJECT_NAME_AT is single valued. thanks Selcuk On Thu, Nov 10, 2011 at 10:51 AM, Emmanuel Lecharny <[email protected]> wrote: > On 11/10/11 7:56 AM, Selcuk AYA wrote: >> >> Hi, >> I have made the changes to use UUID for ID. I have also removed some >> unnecessary type parameters. In particular, master table is not >> generic anymore. For index and index cursors, only value type is a >> generic parameter. Search engine and partitions and tests are changes >> accordingly. Note that counter maintained for ID generation in Btree >> partitions are not necessary anymore. Also, admin table for Jdbm >> parition is removed. One thing I noticed in the tests were implicit >> assumption of master table and indices with the key ID having the same >> order as the insertion order of entries. This assumption is not valid >> anymore as UUID generation is random. > > Great job ! >> >> There is one outstanding issue. Attribute types for system indices >> having UUID as the key has integer comparator as their ordering rule >> in the LDAP attribute type definition. This should be changed to use >> UUID ldap comparator. This is not done yet as I dont know how to do >> it. Instead, we check for specific attribute types during index >> initializations and use UUID comparator if necessary. > > I can handle that. > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > >
