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

fix(db): Rename message_id to _id #172

Merged
merged 10 commits into from
May 20, 2022
Merged

Conversation

grtlr
Copy link
Contributor

@grtlr grtlr commented May 18, 2022

No description provided.

@grtlr grtlr linked an issue May 18, 2022 that may be closed by this pull request
pvdrz
pvdrz previously approved these changes May 18, 2022
Alex6323
Alex6323 previously approved these changes May 18, 2022
@grtlr grtlr changed the title fix(db): index on message.id fix(db): Rename message_id to _id May 18, 2022
@@ -34,8 +34,16 @@ pub struct InfoResponse {

impl_success_response!(InfoResponse);

#[derive(Clone, Debug, Serialize, Deserialize)]
pub struct SyncDataResponse(pub SyncData);
/// An aggregation type that represents the ranges of completed milestones and gaps.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is needed for the syncer, so relegating it to the API is no bueno

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is resolved for now :trollface:

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, we still need it in the syncer

@grtlr grtlr linked an issue May 19, 2022 that may be closed by this pull request
@grtlr grtlr merged commit d5da16a into iotaledger:main May 20, 2022
@grtlr grtlr deleted the message-id-index branch May 20, 2022 09:05
@grtlr
Copy link
Contributor Author

grtlr commented May 20, 2022

I went ahead and merged this, we can add move it later again if we need to, but my goal is to merge #163 too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consolidate db::model and types Find a more suitable name for MongoDb::NAME
4 participants