Unable to sort on computed fields

[robdekort]

When you have computed fields you can't sort listing tables on them. The fields are calculated at run time and not stored in the database. Therefore isn't available for the database to sort on.

I use this

Collection::computed('applications', 'outing_title', function ($entry) {
    return optional($entry->outing)->title;
});

To make sure I can properly sort on an entries field, but alas.

[ryanmitchell]

We should store the computed field values in the database too. I'll work on that.

[robdekort]

You are awesome!

[jackmcdade]

He sure is! ❤️

[AntonCooper]

Would storing these values not become problematic? I've got many implementations of computed fields which require a dynamic values - I thought that was the whole purpose of computed fields, that they're have the ability to be evaluated at runtime?

[ryanmitchell]

The values would be stored so the value at the point of last save could be queried (sorting etc), but when retrieved from the data would be overwritten with your dynamic values. It should cover both use cases.