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.

Sign up for GitHub

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

Jump to bottom

Unintuitive behavior of range on multi-index #430

Closed
hashedone opened this issue Sep 17, 2021 · 0 comments · Fixed by #446
Closed

Unintuitive behavior of range on multi-index #430

hashedone opened this issue Sep 17, 2021 · 0 comments · Fixed by #446
Assignees
@ethanfrey

Comments

@hashedone
Copy link
Contributor

Failing test case can on #429.

Technically it is not a bug, but the behavior seems to make Bound::inclusive not very useful for upper bound of multi index. This whole issue is basically consequence of relying on lexicographical order for comparing keys, and raw &[u8] keys instead of proper key semantics. Somehow related to CosmWasm/cw-storage-plus#10 and #198.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ethanfrey ethanfrey

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add proper prefix_range helper when you want to iterate over the prefix space CosmWasm/cw-plus
2 participants
@ethanfrey @hashedone