Lou King

is this a dup of https://github.com/Pegase745/sqlalchemy-datatables/issues/131?

Not sure, but this might be useful: https://github.com/orf/datatables/blob/dec3acc46898d611ea951b057cecd909c023d086/datatables/__init__.py#L59-L81

> Could you post your code? Like how are you post-processing the data? My code is pretty convoluted because it is embedded in a class which has grown over time....

I already have a workaround for this issue -- this is why I'm adding these to the end. I guess if I really want to make this extension work better...

Thanks. I considered a PR for this one, but don't understand the reasoning behind the current design, and hesitate to make wholesale change suggestions. And I needed a quick "fix"...

Also I just realized the workaround I quoted is only for the object notation handling. My workaround for the index ordering is more complex and would be hard to find...

If I'm understanding your question correctly, I think this is more of a question for [datatables](https://datatables.net/), but columns.title option (https://datatables.net/reference/option/columns.title) can be used so all you have to do is...

This monkey patch seems to take care of the problem for me. Not sure the best term to use rather than `float('inf')`. `sys.maxsize` seemed to be recommended in some of...

It dawned on me that the all_columns call is determining the min and max based on my query. If so this doesn't handle my use case. My initial query returns...

Looks like the easiest way is to create my own class based on DataTables and replace _set_yadcf_data. I'd close this, but maybe you want to consider adding an optional yadcf_data...