On Tue, May 31, 2022 at 02:07:20AM +0000, John Rouillard wrote:
> My guess is it's a holdover from the anydbm key/value store not having
> a native sort method. Also since id's are stored as strings, but
> sorted as integers, we can't use rdbms native sorting on that field.

Umm, I think the original code used IDs as strings. But these days at
least all the sql backends use a numeric field for the id.

And I think that the anydbm code also can sort IDs numerically these
days?!

So I think we *can* use the native order for sorting. See
testFilteringSortId in test/db_test_base.py

But as outlined in another message in this discussion the code I changed
does *not* compare IDs, instead it retrieves the order property (or if
explicitly given, the 'sort_on' parameter) and sorts on that.

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com