You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This scenario requires three thread to all fall into a certain sequence:
Thread A starts a query that takes a long time (implicitly begins read transaction on read connection)
Thread B inserts a document (using write connection)
Thread C retrieves the documents (using read connection)
Thread A finishes
Step 3 will show the document as missing, despite it existing. This is because Thread A has locked the read connection on a stale state with its implicit transaction. There are two ways to fix this:
Serialize queries as well as writes
Let each thread have a separate read connection to the database
Option 2 would be more in line with what iOS does
The text was updated successfully, but these errors were encountered:
Reproduction steps:
This scenario requires three thread to all fall into a certain sequence:
Step 3 will show the document as missing, despite it existing. This is because Thread A has locked the read connection on a stale state with its implicit transaction. There are two ways to fix this:
Option 2 would be more in line with what iOS does
The text was updated successfully, but these errors were encountered: