robconery / dox Goto Github PK

how can we improve on that aspect any idea?

I would love to see dox provide the ability to detect and prevent lost "concurrent" updates. By which I mean concurrent users who retrieve a document in one transaction, then modify it outside the DB and save it back in another transaction.

Maybe dox could keep a version number on each document that increments on every save/modify. The version number could be returned with results. Save and modify could be made to optionally compare the current version number with the one specified in the incoming document and return an error if they don't match.

Wouldn't an index on the specific parts of the JSONB structure be more efficient for what you are looking for? ie:

CREATE INDEX idx_jsonpart ON jsonTbl(cast(body->>'intvalue' AS INT));

No trigger maintenance and it would accomplish what I think you are attempting to accomplish via the lookup. Or am I missing the purpose behind the lookups?

This project is quite interesting and compelling. Can you clarify the license for this code?

Both here in the README.md, and in your blog post, for the dox.save function you use a named argument of 'table', but the function actually uses a parameter 'collection', like the rest of the API.

Hi Rob,
i can able to loop over all the documents and insert but performance prospective we need to insert at a time to all documents,
i read many places that we can use COPY, but how can we use it.
how can we insert bulk of documents into details jsonb and if we insert then how the primary key generate automatically, please help me.

Thanks.