Jan
Jan
There is no time-to-live to configure. Query results will stay in the query results cache until the underlying collections change. Whenever one of the underlying collections changes, the query cache...
Unfortunately I don't know much about Python bindings and how to create them. So I can't really tell where this `ImportError` comes from. I tried creating a small test program...
@mtzonev : The driver tries to turn the query result into an array of `Document` objects by default. This will not work if the returned data aren't actually documents. In...
@wyattwalter : exactly. Unfortunately, a sequence of `@` ... `@` in command-line options (e.g. `@foo@`) is interpreted as a placeholder for environment variables, and will be replaced with the value...
@AntoineAA : in this particular query, the "Unique constraint violated" error can only be triggered by the final UPSERT statement. I didn't try running the exact query because obviously it...
Thanks. I just tried this example, but it works for me. Here is my setup: ```js db.taxa_meta.indexes(); [ { "fields" : [ "_key" ], "id" : "taxa_meta/0", "selectivityEstimate" : 1,...
@AntoineAA : I tried exactly the same sequence of operations, but it still works for me. I am now wondering if the issue is caused by the unique hash index...
@AntoineAA : at least it looks like that. However: I also tried the same but with no luck yet. Thinking more about this, it may indeed have to do with...
@AntoineAA : thanks for trying this out too! I think we will have to try this with replication too then. Though at least in theory having the replication enabled should...
Hi everyone, is there anything that can be done about this issue? It is still causing us lots of problems that auto-recovery does not work with PessimisticTransactionDB even in `WRITE_COMMITTED`...