[389-devel] Re: Trying to understand entryrdn.db

2017-08-03 Thread Nishan Boroian
Let's discuss more on it. > > On Aug 3, 2017 at 07:33, mailto:lkris...@redhat.com)> > wrote: > > > > > On 08/03/2017 12:24 PM, Ilias Stamatis wrote: > > > > > > > > > > That said, whenever you write an entry you always have seen the parent > > > and c

[389-devel] Re: Trying to understand entryrdn.db

2017-08-03 Thread Ludwig Krispenz
On 08/03/2017 12:24 PM, Ilias Stamatis wrote: That said, whenever you write an entry you always have seen the parent and could stack the dn with the parentid and createt the dn without using the entryrdn index. You even need not to keep track of all the entry rdsn/dns - only

[389-devel] Re: Trying to understand entryrdn.db

2017-08-03 Thread Ilias Stamatis
> > That said, whenever you write an entry you always have seen the parent and > could stack the dn with the parentid and createt the dn without using the > entryrdn index. > You even need not to keep track of all the entry rdsn/dns - only the ones > with children will be needed later, the presence

[389-devel] Re: Please review: Draft of the big lib389 and pytest guide

2017-08-03 Thread Simon Pichugin
Hi team, a new version: https://pagure.io/lib389/issue/77#comment-451622 https://pagure.io/lib389/issue/raw/files/6047ac156e06192837271afc2770a83f7f3206400669537bb1d8f43ab7b9a434-Guidelines-for-using-pytest-and-lib389_47541162.html Thanks, Simon On Wed, Jul 19, 2017 at 04:31:50PM +0200, Simon Pi

[389-devel] Please review 49337: CI test - import

2017-08-03 Thread Sankar Ramalingam
https://pagure.io/389-ds-base/issue/49337 https://pagure.io/389-ds-base/issue/raw/files/24b19f4e3af39329fa9c53a67a9cb096e6a8bd536561b261bedb77d642cae179-0001-CI-test-import-bugzilla-test-cases.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproj

[389-devel] Re: Trying to understand entryrdn.db

2017-08-03 Thread Ludwig Krispenz
On 08/02/2017 09:12 PM, Mark Reynolds wrote: On 08/02/2017 02:19 PM, Ilias Stamatis wrote: I see now, thank you both very much! Follow-up: [1] Get entry from id2entry and use its ID [2] Look in entryrdn for the parent of the ID [3] Keep looking for parents, building the DN as