Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
TransactionList cursors can yield duplicate transactions
See original GitHub issuebecause the ordering is newest to oldest a cursor like echo "arrayconnection:1" | base64 could very well return the same transactions multiple times if new transactions have occurred which would invalidate the state of the last cursor.
We must either reverse the default order of transactions or change the way we represent cursor.
How is this currently handled in the mobile app @daviroo ?
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Duplicates Cause Rollback Transaction
So, in your example, executing an insert statement that gets a duplicate key error, while a cursor is open, will cause the entire...
Read more >Duplicate transactions; Transaction sheet functionality broken
Hi, the exact same things are happening to me since the Refresh All button was removed - duplicates and no data validation. I've...
Read more >Visa Reason Code 12.6.1: Duplicate Processing
Visa reason code 12.6.1 applies when the issuing bank receives the same transaction more than once, or the cardholder claims a double charge....
Read more >Why do I see duplicate transactions in my account?
Currently, our system is not designed to automatically check for duplicate transactions between most carts, as our integrations were designed ...
Read more >Python, SQLite3: cursor returns duplicates when a commit ...
Cursors maintain their own prepared statement lists which are separate from Connection objects. You can either explicitly create a cursor OR ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The apollo docs recommend using element IDs for cursors https://www.apollographql.com/docs/react/pagination/cursor-based/#using-list-element-ids-as-cursors. I guess using the transaction ID as the cursor would fix the issue.
This would not fit the use case from mobile/web wallet where we show the most recent tx