Long running queries interfere with the next query in the same card

[alfredorubin96]

• NeoDash version: 2.4.1

• Neo4j Database version: Probably any.

• Expected behavior

  1. Set a parameter that triggers the run of a long running query (in my case it was long enough to go in transaction timeout)
  2. In the middle of the run, change parameter, re-triggering the query
  3. After the run of the second query, the card will pop-up the result of the second query, without showing the result of the first query (kill the transaction at the start of the new one)

• Actual behavior

  1. Set a parameter that triggers the run of a long running query (in my case it was long enough to go in transaction timeout)
  2. In the middle of the run, change parameter, re-triggering the query
  3. After the run of the second query, the card will pop-up the result of the first query, after a certain amount of time that is the delta between the two executions.

Additionally, include (as appropriate) screenshots, drawings, etc.

[nielsdejong]

@alfredorubin96 i looked into this and think I know how to fix it - we need to remember the transaction object across query executions and then cancel any existing transactions for the same card upon execution of the new one. Unfortunately this is kind of a big architectural overhaul... so I propose we park this for later.