Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always use transfers_block_num for transfers by default #36

Merged
merged 1 commit into from
May 30, 2024

Conversation

0237h
Copy link
Collaborator

@0237h 0237h commented May 30, 2024

When querying with no parameters, the default is to query transfer_events. However since the ORDER BY clause specify the block_number it will slow down the query significantly.

Changing the default to always use the transfers_block_num MV table helps solve the issue.

When querying with no parameters, the default is to query `transfer_events`.
However since the `ORDER BY` clause specify the `block_number` it will slow
down the query significantly.

Changing the default to always use the `transfers_block_num` MV table helps
solve the issue.
@0237h 0237h self-assigned this May 30, 2024
@github-actions github-actions bot added the bug Something isn't working label May 30, 2024
@0237h 0237h merged commit aab2b63 into main May 30, 2024
2 checks passed
@0237h 0237h deleted the fix/default_transfers_table branch May 30, 2024 21:09
0237h added a commit that referenced this pull request May 30, 2024
When querying with no parameters, the default is to query `transfer_events`.
However since the `ORDER BY` clause specify the `block_number` it will slow
down the query significantly.

Changing the default to always use the `transfers_block_num` MV table helps
solve the issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant