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

services/horizon: Add Muxed Account details to effect responses #3610

Merged
merged 3 commits into from
May 23, 2021

Conversation

2opremio
Copy link
Contributor

@2opremio 2opremio commented May 19, 2021

Addresses part of #3591

Depends on #3603 (whose commits are included here for now)

TODO:

  • Add more tests

@2opremio 2opremio force-pushed the 3591-add-muxed-details-to-effects branch from b0be928 to 0399bd5 Compare May 20, 2021 16:21
@2opremio 2opremio marked this pull request as ready for review May 20, 2021 16:21
@2opremio 2opremio requested a review from a team May 20, 2021 16:21
Copy link
Contributor

@Shaptic Shaptic left a comment

Choose a reason for hiding this comment

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

Added some thoughts about whether or not we can unify code paths to always use the MuxedAccount object.

@2opremio 2opremio force-pushed the 3591-add-muxed-details-to-effects branch 2 times, most recently from ba9bec4 to a623765 Compare May 21, 2021 10:11
Copy link
Contributor

@bartekn bartekn left a comment

Choose a reason for hiding this comment

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

LGTM! Added two questions/ideas.

// We abuse the details to inject muxed-account information without changing the DB schema
details["account_muxed"] = address.Address()
details["account_muxed_id"] = uint64(address.Med25519.Id)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry, this might have been discussed in previous PR but why not add a new column to the table? Adding a DEFAULT NULL column is fast as far as I can remember.

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 discarded that because I agreed with @ire-and-curses to minimize schema changes.

That said, if we agree to make a schema change, it would also solve the performance problem with #3619

Copy link
Member

Choose a reason for hiding this comment

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

ok, let's add the column. I don't like having to deserialise the whole envelope every time. Lesser of two evils.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK, I will merge this as is and then change the approach.

@2opremio 2opremio force-pushed the 3591-add-muxed-details-to-effects branch from a623765 to 6bd8790 Compare May 21, 2021 17:09
@2opremio 2opremio force-pushed the 3591-add-muxed-details-to-effects branch from 6bd8790 to 43c2435 Compare May 23, 2021 23:10
@2opremio 2opremio merged commit a11d444 into stellar:master May 23, 2021
This was referenced Jun 2, 2021
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.

None yet

5 participants