I want to sort SQL pagequeries naturally

[vaniwiki]

I am making a view that shows me a card for each chapter within that book. These chapters are called 1:start, 2:start, 3:start and so on, up to twenty, thirty chapters or more. Which means they will display 1:start, 10:start, 11:start... I would like to be able to sort them naturally 1, 2, 3 before 10, 11, 12. Just wondering if anyone knows.

<iterator>
    <data>select where path like '%books:bg:%' and path like '%start%' order by path asc</data>
    <card-columns>
        <fragment>
            <card clickable>

            === $label ===

            ${description | head(1024,'...')} [[$path?preview=false| ]]
            </card>
        </fragment>
    </card-columns>
</iterator>

[gerardnico]

It should work. The engine is SQLLite therefore this is the sorting of Sqlite.
See doc: https://sqlite.org/datatype3.html#sorting_grouping_and_compound_selects

[gerardnico]

The only way would be to have a numeric sort field but Combo does not have one.

[vaniwiki]

Not even the date_published, and work in incremental date values?

[gerardnico]

I don't understand what you wrote and what you want to do.

giving examples with your writing helps your message to be better brought over.

I have other things to do today. Therefore pardon my future silence. Wish you the best.

[vaniwiki]

Sorry. I don't mean to take so much of your time. This information I should be able to glean from other places...

On your page here it seems you are saying that the attributes, or variables(?) on this page can be used to sort by. I assumed that I could use the date_published attribute and sort by that. Gives me plenty of numbers to work with, days, months, even years.

Speech is silver, and silence is golden. Wish you a blessed day. :)

[vaniwiki]

It actually worked to sort with the date_published attribute. The fault lay in my query somewhere. Now it reads:

<data path=":books:lob:">select from descendants order by date_published asc</data>

Which works. It is cumbersome to do all pages like that, but maybe if I set a secondary sort option, I can get away with having to set date_published only on the first nine pages. That is, if total pages are under 100. Else, the first 99. Let me try...

As long as I can find a workaround, I'm not gonna complain. Just sharing. :)