> If the column value is numeric, why not just use math calculation?
Thats the whole problem : *I don't know* what the (random, user-selectable)
"sort on" column will contain. If I would know for a fact that that column
contains just numbers I would (not need to) bother with the
string-comparision length at all ...
IOW: Fine-tuning the WHERE for numeric use will (probably?) clash with a
columns string contents, and fine-tuning it for string comparision will (as
experienced) clash with the columns numeric contents. :-|
One possibile solution would be if I could tell the DB that the comparision
should be done in accordance with the columns type specification, instead of
letting the WHERE clause dictate it (like the use of SUBSTRING forcing a
string comparision). The problem is that I simply do not know enough about
sqlite3 to even be aware of possible roads to investigate.