Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

KeyRange.atLeast vs KeyRange.atLeastBackward with out-of-bound value #86

Closed
@creambun

Description

@creambun

Hi there,

I am not sure if the behavior described below is as expected because I cannot yet find relevant document. If there is, please kindly let me know

The behavior I found is that KeyRange.atLeast can iterate over all records even if the given key range value is smaller than the key of the first record, while KeyRange.atLeastBackward cannot even iterate one record if the given key range value is greater than the key of the last record. It is best illustrated below:

Data in db: {2, "22"}, {4, "44"}, {6, "66"}, {8, "88"}
Search with KeyRange.atLeast and start with key = 1 -> all records can be iterated. I have no question about this
Search with KeyRange.atLeast and start with key = 2 -> all records can also be iterated. I have no question about this
Search with KeyRange.atLeastBackward and start with key = 8 -> all record can be iterated backward. I have no question about this either
Search with KeyRange.atLeastBackward and start with key = 9 -> no record can be iterated. I am quite surprised

Can anyone please give me some hint / help? Thanks

JUnit test code can be found in the attached file test.zip

test.zip

Metadata

Metadata

Assignees

No one assigned

    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


      [8]ページ先頭

      ©2009-2025 Movatter.jp