Skip to content

Unintuitive behavior of range on multi-index #430

@hashedone

Description

@hashedone

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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions