Hi,
Is it possible to add a set of attribute to an entry,
instead of adding one by one? That would be like a
struct in C, for example
myattr { departmentnumber, manager }
and I would access it
(myattr.manager=john)
or something like that.
thanks
sz
__________________________________
Yahoo! Music Unlimited
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/
What programming language are you using? speedy zinc wrote:>Hi, > >Is it possible to add a set of attribute to an entry, >instead of adding one by one? That would be like a >struct in C, for example > >myattr { departmentnumber, manager } > >and I would access it > >(myattr.manager=john) > >or something like that. > >thanks > >sz > > > > >__________________________________ >Yahoo! Music Unlimited >Access over 1 million songs. Try it free. >http://music.yahoo.com/unlimited/ > >-- >Fedora-directory-users mailing list >Fedora-directory-users@redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users > >
Actually, I''m asking this not from a programming language point of view, but from a schema point of view. Right now, each attribute seems to be independent of each other. I have to add them one at a time. I''m looking to group related attributes into a higher level object, and add it to an entry. So, when my app is looking into the entry, it can look into that set of attributes. For example, I have my HR app, let''s say I create a schema, and I want to call my set of attr hrApp, which contains departmentnumber, manager, ... So when I do ldapsearch, instead of using (manager=john) I can do (hrApp.manager=john) that would be used as "standard" ldap query syntax :) I''m looking at the CoS, but really don''t know how to use it. The concept of CoS seems like aspect programming to me, but my understanding from the manual is that, the value of attributes in CoS is shared by the entries, and not the definition. How could I define a CoS, where the value of attributes is not set, and apply it to entries, or set of entries, and each entry may set a different value to the CoS? thanks sz --- Rich Megginson <rmeggins@redhat.com> wrote:> What programming language are you using? > > speedy zinc wrote: > > >Hi, > > > >Is it possible to add a set of attribute to an > entry, > >instead of adding one by one? That would be like a > >struct in C, for example > > > >myattr { departmentnumber, manager } > > > >and I would access it > > > >(myattr.manager=john) > > > >or something like that. > > > >thanks > > > >sz > > > > > > > > > >__________________________________ > >Yahoo! Music Unlimited > >Access over 1 million songs. Try it free. > >http://music.yahoo.com/unlimited/ > > > >-- > >Fedora-directory-users mailing list > >Fedora-directory-users@redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > > > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users>__________________________________ Yahoo! Mail - PC Magazine Editors'' Choice 2005 http://mail.yahoo.com
> -----Original Message----- > From: fedora-directory-users-bounces@redhat.com > [mailto:fedora-directory-users-bounces@redhat.com] On Behalf > Of speedy zinc > Sent: Tuesday, October 18, 2005 5:38 PM > To: General discussion list for the Fedora Directory server project. > Subject: Re: [Fedora-directory-users] set of attributes? > > For example, I have my HR app, let''s say I create a schema, > and I want to call my set of attr hrApp, which contains > departmentnumber, manager, ... > > So when I do ldapsearch, instead of using > > (manager=john) > > I can do > > (hrApp.manager=john) > > that would be used as "standard" ldap query syntax :)OK I think I understand what you don''t understand :) The objectclass attribute values are like your hrApp, in that they are what determine which attributes an entry _must_ have and which attributes an entry _may_ have. So, taking the inetorgperson objectclass, which happens to allow the manager attribute (which is dn syntax so it points to the manager entry itself) your filter would be: (&(objectclass=inetorgperson)(manager=uid=john,dc=my,dc=org))> > I''m looking at the CoS, but really don''t know how to use it. > The concept of CoS seems like aspect programming to me, but > my understanding from the manual is that, the value of > attributes in CoS is shared by the entries, and not the definition. >Yes it is a way to share common attribute/value pairs among many entries - not really what you are after.