-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
db: rename kv Query to Request #2768
Conversation
184a1f0
to
a9bd934
Compare
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.
That looks good.
I just have one thought: can we apply similar logic to silkworm::datastore::kvdb:: and silkworm::db::state::?
Or maybe use a different approach and apply the following naming convention:
- DomainGetLatestQuery -> DomainGetLatestQuery
- DomainPutQuery -> DomainPutCommand
- DomainDeleteQuery -> DomainDeleteCommand
I know it's a minor thing but things like DomainPutQuery
might be confusing
@@ -1050,14 +1050,14 @@ int kv_get_latest() { | |||
const auto verbose{absl::GetFlag(FLAGS_verbose)}; | |||
|
|||
if (timestamp > -1) { | |||
GetAsOfQuery query{ | |||
GetAsOfRequest query{ |
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.
GetAsOfRequest query{ | |
GetAsOfRequest request{ |
.table = table_name, | ||
.key = *key_bytes, | ||
.timestamp = timestamp, | ||
}; | ||
return execute_temporal_kv_query(target, kv_get_as_of_query, std::move(query), verbose); | ||
} | ||
GetLatestQuery query{ | ||
GetLatestRequest query{ |
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.
GetLatestRequest query{ | |
GetLatestRequest request{ |
@JacekGlen thanks for the review, let's discuss it further live. I'll address the found leftovers in a follow up PR. |
No description provided.