helpers.format makes sorting work as if column is text rather than numeric

[pivotal-energy-solutions]

helpers.format makes sorting work as if column is text rather than numeric

[tiliv]

Hm... does the middle argument of the column definition correctly reflect a database value, or is it computed via a method?

It sounds like the code is deciding it's not a real database field, and it's manually sorting by post-processed version of the data.

To prevent this, make sure the value's model field is correctly specified as part of the column definition:

datatable_options = {
    'columns': [ ('My Field', 'path__field', helpers.callback("{0:,}")) ],
}

If the field is calculated and not actually available at the query level, you can specify a model method/property name, and then you'll have to return a 2-tuple of data from your datatable callback so that it knows what is "formatted" and what is "raw":

datatable_options = {
    'columns': [ ('My Field', 'path__field', helpers.callback("{0:,}")) ],
}
def get_column_My_Field_data(self, obj, *args, **kwargs):
    text = "{0:,}".format(obj.path.field)
    return (text, obj.path.field)

I think this managed to escape full documentation. I'll see what I can do to add that in. It's not the kind of thing you want to be forced into doing often, but let me know if it changes anything.

[bmatzelle]

Hm... does the middle argument of the column definition correctly reflect a database value, or is it computed via a method?

It's computed by a method.

If the field is calculated and not actually available at the query level, you can specify a model method/property name, and then you'll have to return a 2-tuple of data from your datatable callback so that it knows what is "formatted" and what is "raw"

Excellent! Thanks for the help!