Re: mdb_dbi_open and threads

To: Klaus Malorny <Klaus.Malorny@knipp.de>

Subject: Re: mdb_dbi_open and threads

From: Muhammed Muneer <elendilm@gmail.com>

Date: Fri, 4 Aug 2017 07:31:01 +0400

Cc: Howard Chu <hyc@symas.com>, openldap-technical@openldap.org, Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yVTZNNABVs/PRtTGKr9YO+cS88ql+d1hVEtTRP/i53k=; b=tQV1VKAGsMZ7f60nIpdUr2ed8eXBqDQ7FklFfw652fBnR4e96zkHvVfx3nayJFqiFS K1a43R6N4B05qhbvOWSOCd3jH2tppa4yFfeKstgYwnpikb6ZCxNW/p3fU0N13MIouRBn CYbJsWxtPu7f81Nd56KD1uISEtFTPtmMXGoCoOHwt5gpxqrLtV/ritQuIQ3cox7Iru60 09hqw40fxsp7GM1LeIbpbTrWfaFiMqkrZJg5X8nnNEJt70LOkEM9mkxeG6PdP7A3V7fn rLWZ3ZYWIy0HPTzQtxQs982++pEI61gm2p4P+X2FwqJy0yuMvAZdW6rc+L5rjrhjsJdv yEZw==

In-reply-to: <CAMvTE2NS5DdABGgyjsgzp_wgogsOHmWsZD0aOdQwOmy2O_yTxA@mail.gmail.com>

References: <CAMvTE2PoED94-ZiGjCHt+akiYSjqQvFqkYe3Z7DHdkGdcwdSQA@mail.gmail.com> <450e4835-9c54-0c5c-29cd-ab081eee8bd0@symas.com> <CAMvTE2N2k-O-_f-u-ChdBv+BZmkkidqUMsp4pp9PmcWRSOaCiA@mail.gmail.com> <CAMvTE2MjUBZ0YdzYxXVUnDGuawicuUDH3Y4Vy-pt3PidFgxrXg@mail.gmail.com> <4ee53713-f261-7efe-97cb-66e834f0f86b@knipp.de> <CAMvTE2OdV_MxeH=F1NfTjSOXe48zow330v4e1c185yvVedeREg@mail.gmail.com> <WM!fca24ec35fb2ea6029fe6df0c81746209810835b76c57bfceee80ab2ef6796789549c5df115c82370b14612c57e1d98e!@mailstronghold-1.zmailcloud.com> <611b7680-366a-6ad6-3b6f-47922bf88940@symas.com> <f7441608-0c22-6ebd-5c85-dde1ead68fdd@usit.uio.no> <WM!233e16a5e3ba4174ba4546004358dfbbf29cec9059486b9a0982c3561a2342529c272b5c17bbce035ad5074ff377f5a3!@mailstronghold-3.zmailcloud.com> <8db837aa-51bf-39af-1217-55d69cc20099@symas.com> <CAMvTE2PFDczxGFTVCpZHgjYWDGtoRu=jYaEtxYy3PwZbwg5Z7w@mail.gmail.com> <2c181331-fa75-288c-5d59-cc6c66ab6f05@knipp.de> <CAMvTE2NS5DdABGgyjsgzp_wgogsOHmWsZD0aOdQwOmy2O_yTxA@mail.gmail.com>

Sorry for the late reply.

I finally went with the solution Klaus Malorny stated. Storing all the data in in one big database named "main" and prep-ending a 4 byte int (database id or collection id) to the key.
These collection ids are stored in a seperate database named "collections".
And the query handler has been modified to take care of the "range" queries that corresponds to a logical database.

Thanks for all the response and suggestions.

On Mon, Jun 19, 2017 at 6:52 PM, Muhammed Muneer <elendilm@gmail.com> wrote:

I know. But that is not my problem.

On Mon, Jun 19, 2017 at 2:31 PM, Klaus Malorny <Klaus.Malorny@knipp.de> wrote:
On 6/19/17 10:31 AM, Muhammed Muneer wrote:

Sorry for the late reply, I was on vacation.

Klaus wrote:
"I am still unsure what you are trying to achieve. If you are in a read transaction and discover that your database does not exist, what can you do anyway? You cannot create the database at this point, since it is a write operation."

When I discover a dbi does not exist in a read transaction, I can assume it to be the same as a dbi which is empty and create it when and only when there is a write-request into that dbi later.

To my understanding, the API does not prevent you from doing so. As long as you do not specify the MDB_CREATE flag, you can call mdb_dbi_open and will get informed whether the database exists or not (MDB_NOTFOUND).

Klaus