Feature request: Sorting index-query results by index key. about lex.db

[emanuelpalm]

I guess an alternative would be to add the possibility of re-sorting an entire index. If I provide one StringComparer the first time the table is instantiated, and then another is provided the next time, then if the table index would be re-sorted then that would also be great.

[demigor]

Lex.DB cannot preserve the exact comparer used to create an index. So automatic resorting is basically not possible.

What probably is the easiest solution it is to provide index resorting methods.

From: Emanuel Palm [mailto:[email protected]]
Sent: Monday, 21 December 2015 10:37 AM
To: demigor/lex.db [email protected]
Subject: Re: [lex.db] Feature request: Sorting index-query results by index key. (#36)

I guess an alternative would be to add the possibility of re-sorting an entire index. If I provide one StringComparer the first time the table is instantiated, and then another is provided the next time, then if the table index would be re-sorted then that would also be great.

—
Reply to this email directly or view it on GitHub #36 (comment) . https://github.com/notifications/beacon/ACo4ISxeBAlLuraSpA-bG4eSF9YSwwCqks5pR7-kgaJpZM4G5GAe.gif

[emanuelpalm]

👍 Index resorting would be great. Thanks for quick reply, btw.

Is this something you feel you could easily throw together? Otherwise if you could give me a few hints about which classes I would need to update, I could probably start working on a PR sometime in January.