Sorting on numeric custom columns?

[rmzg]

In a desperate attempt to get calibre to show the actual order in which I've added books I created a custom column that shows calibre's internal id for each book, which conveniently is a simple integer that increments every time you add a book.

I've told CC to add this custom column to be available to sort by, and it is, except it sorts in ascii mode such that 900 comes after 8000, which is slightly awkward.

How to fix?

[theducks]

Originally Posted by rmzg

In a desperate attempt to get calibre to show the actual order in which I've added books I created a custom column that shows calibre's internal id for each book, which conveniently is a simple integer that increments every time you add a book.

I've told CC to add this custom column to be available to sort by, and it is, except it sorts in ascii mode such that 900 comes after 8000, which is slightly awkward.

How to fix?

{id} is an Integer, not text

You could pad those with less than 5 digits with leading 0's using Bulk Mode Search and Replace you have 8000 already, so I suggest 5 digits now and worry when you hit 100K

[rmzg]

Am I supposed to use bulk mode from companion or calibre itself? How will this handle new books that are added/transferred?

And I mean, I know it is an integer, can companion not sort integers at all?

[DoctorOhh]

Originally Posted by rmzg

And I mean, I know it is an integer, can companion not sort integers at all?

I think his point is the custom column type has to be an integer custom column and not a text custom column type. You can place numbers in a text custom column, but I suspect a text column will sort on ascii, thus the suggestion to pad the numbers with zeros. Is your custom column a text type or integer type custom column?

[rmzg]

I'm still a little confused what you mean by text vs integer columns, is this the setting inside calibre itself? This is how I created the actual column.

Are you suggesting I change the template to display padded with zeroes?


http://i.imgur.com/VyACh2i.png

[DoctorOhh]

Originally Posted by rmzg

I'm still a little confused what you mean by text vs integer columns, is this the setting inside calibre itself? This is how I created the actual column.

Are you suggesting I change the template to display padded with zeroes?


http://i.imgur.com/VyACh2i.png

It looks like I was confused. The way you created the column I would have assumed that CC would sort it accurately. It certainly sorts accurately in calibre.

I guess @chaley will have to let us know why the sort is off or what we are missing.

[rmzg]

I think I discovered something, if you select "column built from other columns, behave like tags" then you get some additional options, one of which is ...

Ok I thought there was something different but now I'm just confused. I built a new column with "behave like tags" and it seems to be sorting more accurately but it's a bit glitchy inside companion.

[rmzg]

Reply to myself: Ha Ha just kidding! It kinda sorta worked after I resynced then I ran 'rebuild database' and now it's back to sorting as a string. INFINITE SADNESS.

[chaley]

CC sorts custom integer and float columns as numbers.

Composite columns are always text, the result of evaluating a template, and that is how CC sorts them. CC does not take the calibre "sort hint" into account. If you want a "id" composite column to sort like a number in CC then you must fill it with leading zeros using something like

{id:09d}