Russell Wilton wrote:
> David J Kernen wrote:
>
> > I doubt that ldapsearch (and similarly but in an opposite direction,
> > ldapmodify) do anything special to maintain order; they just process
> > what they're given in the order they receive it because that's the
> > easiest way.
>
> That's all
David J Kernen wrote:
> I doubt that ldapsearch (and similarly but in an opposite direction,
> ldapmodify) do anything special to maintain order; they just process
> what they're given in the order they receive it because that's the
> easiest way.
That's all I wanted Perldap to do too. Just pro
Russell Wilton wrote:
> To say that this violates the protocol, implies that the ldapmodify
> and ldapsearch programs distributed with the Netscape LDAP also
> violate the protocol, since they maintain attribute order.
Sorry, but I still disagree. The ldapsearch command is stream-oriented,
whic
David J Kernen wrote:
Wrong. Perldap is behaving according to the protocol.
(See below.)
I agree. Perldap is not required to return the attributes in any
particular order.
This feature would place perldap in direct violation
of the LDAP protocol.
Here I disagree with you. As the RFC says, the o
Russell Wilton wrote:
Hi:
Thanks for your replies. You both said pretty much the same thing
- it can't
be done. I trust you will agree that when you create a record
with
ldapmodify, the attributes are stored in the order you enter them,
and when
you retrieve the record with ldapsearch, the reco
Hi:
Thanks for your replies. You both said pretty much the same thing - it can't
be done. I trust you will agree that when you create a record with
ldapmodify, the attributes are stored in the order you enter them, and when
you retrieve the record with ldapsearch, the record is returned with th
Russ Wilton wrote:
>
> attributes stored in a particular order? I pass the data to Perldap
> using calls to "entry->setValues" in the order I want the attributes
> stored, but they end up in a different order in the LDAP database, as
> shown by retreiving the entry with ldapsearch. Am I missing
attributes stored in a particular order? I pass the data to Perldap
using calls to "entry->setValues" in the order I want the attributes
stored, but they end up in a different order in the LDAP database, as
shown by retreiving the entry with ldapsearch. Am I missing something
here, or is it not
