-
Notifications
You must be signed in to change notification settings - Fork 90
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
[EASY] Update most_recent_cip_20_data #2997
Conversation
const QUERY: &str = r#" | ||
SELECT * | ||
FROM settlement_observations so | ||
JOIN settlements s ON s.log_index = so.log_index AND s.block_number = so.block_number | ||
WHERE s.tx_hash = $1 | ||
WHERE s.tx_hash = ANY($1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably avoid using Postgres-specific syntax.
pub async fn fetch( | ||
ex: &mut PgConnection, | ||
tx_hash: &TransactionHash, | ||
) -> Result<Option<Observation>, sqlx::Error> { | ||
tx_hashes: &[TransactionHash], | ||
) -> Result<Vec<Observation>, sqlx::Error> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the table is used only for debugging and never queried outside the e2e tests, right? How about specifying this right in the docs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean in the database readme or?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, in the readme.
Description
Fixes #2992
settlement_scores::fetch
will be updated once the #2980 is merged.How to test
Existing univ2 e2e test.