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
The problem is that people usually use it either to get the entire transaction history with arbitrary events or to get the recent actions that happened
Problem Definition
Why do we need this feature?
For example, it helps not to query each page, get the key for the next and query the same size page to reach the end (as a consequence we query all history but need only the tail)
What problems may be addressed by introducing this feature?
Node overloaded by high amount of queries performed only for 1 page at the end
What benefits does the SDK stand to gain by including this feature?
One would be safe to assume that SDK itself doesn't get any benefits in general
Are there any disadvantages of including this feature?
It's a minor issue so don't think It'll somehow expand the codebase or give any disadvantages. More benefits than efforts
Proposed Feature
It would be nice if cosmos-sdk would include reverse (boolean) option in QueryTxsByEvents function to facilitate the effort in reaching the latest transactions performed with certain events
The text was updated successfully, but these errors were encountered:
digging through the code i see that QueryTxsByEvents already accept orderBy string in the argument which supports ascending and descending. Dont know if this is provides the same feature you are requesting ?
Summary
The problem is that people usually use it either to get the entire transaction history with arbitrary events or to get the recent actions that happened
Problem Definition
For example, it helps not to query each page, get the key for the next and query the same size page to reach the end (as a consequence we query all history but need only the tail)
Node overloaded by high amount of queries performed only for 1 page at the end
One would be safe to assume that SDK itself doesn't get any benefits in general
It's a minor issue so don't think It'll somehow expand the codebase or give any disadvantages. More benefits than efforts
Proposed Feature
It would be nice if cosmos-sdk would include reverse (boolean) option in QueryTxsByEvents function to facilitate the effort in reaching the latest transactions performed with certain events
The text was updated successfully, but these errors were encountered: