On 08/22/2017 01:31 AM, William Brown wrote:
I have a question / concern though. I thought that we want dbscan 2
ldif for emergency recovery scenarios when all else has gone bad and
assuming that id2entry is still readable. In the approach you
described we make the assumption that the parentid
> >
> > I have a question / concern though. I thought that we want dbscan 2
> > ldif for emergency recovery scenarios when all else has gone bad and
> > assuming that id2entry is still readable. In the approach you
> > described we make the assumption that the parentid index is readable
> > as
2017-08-17 12:27 GMT+03:00 Ludwig Krispenz :
> Hi,
> Ilias' proposal follows the db2ldif approach and I think it will work,
> even if it might need some tweaks to handle multiple out of order oparents.
>
> An other option would be to follow the total update approach using the
2017-08-17 3:55 GMT+03:00 William Brown :
> On Tue, 2017-08-15 at 22:03 +0300, Ilias Stamatis wrote:
> > 2017-08-15 9:56 GMT+03:00 William Brown :
> >
> > > On Fri, 2017-08-11 at 17:49 +0300, Ilias Stamatis wrote:
> > > > Hi everybody,
> > > >
> > > >
Hi,
Ilias' proposal follows the db2ldif approach and I think it will work,
even if it might need some tweaks to handle multiple out of order oparents.
An other option would be to follow the total update approach using the
parentid index and direct get from id2entry.
You start with the suffix
2017-08-15 9:56 GMT+03:00 William Brown :
> On Fri, 2017-08-11 at 17:49 +0300, Ilias Stamatis wrote:
> > Hi everybody,
> >
> > Following Ludwig's and Mark's suggestions on how to perform a database
> dump
> > in LDIF format from dbscan, I have come up with a strategy. I'm
On Fri, 2017-08-11 at 17:49 +0300, Ilias Stamatis wrote:
> Hi everybody,
>
> Following Ludwig's and Mark's suggestions on how to perform a database dump
> in LDIF format from dbscan, I have come up with a strategy. I'm talking
> about ticket #47567: https://pagure.io/389-ds-base/issue/47567
>
>