Josipmrden

@dgarros Are those queries also write queries? Can you share an example? We will also see into the retry logic of the drivers. What driver are you currently using when...

https://github.com/memgraph/memgraph/pull/1361 This is the main PR so far associated with the issue. It enables retry logic from the driver side, and you will not need to worry about implementing manual...

As for the handling of concurrent writes in general in the Memgraph database, we're conducting an investigation whether we can relax in any way the importing to at least solve...

@dgarros We merged PR https://github.com/memgraph/memgraph/pull/1361 which has changed which exception is thrown when the conflict is happening. The behaviour will now be that clients will out of the box be...

With the PR https://github.com/memgraph/memgraph/pull/1361 this will be handled better with the drivers. The goal is to run managed transactions, and have the retry logic with exponential backoff out of the...

@jngarber-st Memgraph v2.12 Should be released today with that fix, so stay tuned! If you have time after download, please do comment on how did the new version with the...

@gitbuda please update this issue with examples

From my perspective there are multiple ways to assess the issue: 1. Enabling the user to delete the whole database without waiting for the match (n) detach delete n; to...

> ``` > STORAGE MODE IN_MEMORY_ANALYTICAL; > CREATE CONSTRAINT ON (e:TEMP) ASSERT e.id_entity IS UNIQUE; > CREATE (e:TEMP {id_entity: 1}); > CREATE (e:TEMP {id_entity: 1}); > MATCH (n:TEMP) RETURN n;...

Reproduced the issue. The issue is happening during commit time in the analytical mode. Since there are no delta objects being created in the analytical mode, we don't go through...