Re: [Fwd] Writing in nonascii (binary) format

2003-05-31 Thread Neo -
I didn't know ldapsearch is b64 encoding ...got it. Thanks all for your valuable feedback. -Neo Graham Barr <[EMAIL PROTECTED]> wrote: On Thu, May 29, 2003 at 12:15:23PM -0700, Neo - wrote: > No graham i am not using LDIF module . > > Just reading the values from ldapsearch command i knew e

Re: [Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Peter Marschall
Hi, On Thursday 29 May 2003 20:34, Clifton, Doug wrote: >I have experienced the same results when using straight .ldif files to > load some of the directory servers, but I've not made a definitive study to > see why. The values reload and match properly from what I've experienced, > so we nev

Re: [Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Graham Barr
On Thu, May 29, 2003 at 12:15:23PM -0700, Neo - wrote: > No graham i am not using LDIF module . > > Just reading the values from ldapsearch command i knew excatly which entry has that > particular leading space problem . > > here is the sample snap shot > > D:\>ldapsearch -h hostname -p port

Re: [Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Chris Ridd
On 29/5/03 8:15 pm, Neo - <[EMAIL PROTECTED]> wrote: > No graham i am not using LDIF module . > > Just reading the values from ldapsearch command i knew excatly which entry has > that particular leading space problem . > > here is the sample snap shot > > D:\>ldapsearch -h hostname -p port -w -b

Re: [Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Neo -
No graham i am not using LDIF module . Just reading the values from ldapsearch command i knew excatly which entry has that particular leading space problem . here is the sample snap shot D:\>ldapsearch -h hostname -p port -w -b "filter" objectClass: top objectClass: person objectClass: organi

Re: [Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Graham Barr
On Thu, May 29, 2003 at 09:15:23AM -0700, Neo - wrote: > This is follow-up of my pervious question ...when i try to add values say > > CN=" test"; (Having a white space character in front) > > or name =" "; (null value) If you are using LDIF tou output the entries then any attribute where the

Re: [Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Clifton, Doug
Neo, I have experienced the same results when using straight .ldif files to load some of the directory servers, but I've not made a definitive study to see why. The values reload and match properly from what I've experienced, so we never bothered about it further. It seemed that the single

Re: [Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Chris Ridd
On 29/5/03 5:15 pm, Neo - <[EMAIL PROTECTED]> wrote: > This is follow-up of my pervious question ...when i try to add values say > > CN=" test"; (Having a white space character in front) > > or name =" "; (null value) > > i expected the values as cn= test; > but when i read the cn attribute in

Re: [Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Neo -
This is follow-up of my pervious question ...when i try to add values say CN=" test"; (Having a white space character in front) or name =" "; (null value) i expected the values as cn= test; but when i read the cn attribute in directroy server its giving me in non readable format like VGVzd

[Fwd] Writing in nonascii (binary) format

2003-05-30 Thread Graham Barr
- Forwarded message from Neo - <[EMAIL PROTECTED]> - Date: Thu, 29 May 2003 08:41:09 -0700 (PDT) To: [EMAIL PROTECTED] From: Neo - <[EMAIL PROTECTED]> Subject: Writing in nonascii (binary) format Hi grahm, I am new bee to net ldap your documentation really helped me to get through all my