Bug: < on indexed column

[plentylife]

This is a kind of funny bug.

I have a column like this
{key: 'lastNotification', type: 'number', props: ['idx']}
and a query like this
nSQL(TABLE).query('select').where(['lastNotification', '<', before]).exec()

The above does not work.
If I remove 'idx' from the column, it works
OR if I switch '<' to '<=' it works

[only-cliches]

Thanks for the bug report, I'll have this patched in the next release.

[only-cliches]

Alright, just pushed v1.5.5, range queries with secondary indexes have been resolved.

[plentylife]

Thank you! I do not tire of saying how awesome you are. This is the best support I have ever gotten.

…

On Sun, May 13, 2018 at 10:52 AM, Scott Lott ***@***.***> wrote: Alright, just pushed v1.5.5, range queries with secondary indexes have been resolved. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ads01GGfHH-rR_QuQSS6iMXrkOG2qHC8ks5tyEiygaJpZM4T8k4s> .

[only-cliches]

Awesome to hear, thanks man! Marking this one resolved..

[plentylife]

I'm on 1.5.8 now and there's an opposite issue
Querying with '>' on an indexed column does not work :)

[only-cliches]

1.5.9 should resolve things, I added tests as well so we don't get feature/bug regression.

[plentylife]

Confirmed. Thank you.