include a non-selected, computed SQL property.

[bennadel]

I'm not sure if this is a good way to use the Wheels models. But, I like that you can define arbitrary properties using SQL. But, it's not so easy to get that pulled into a query unless it's selected by default. It would be interesting to be able to include them into the .find* method as part of the include, maybe with a sql: prefix. Exmaple:

Without this, I have to explicitly spell out the select clause and include the computed property.

[bennadel]

Also very open to any other suggestions on how to handle this kind of aggregate data. In this case, I often want to show it in either a search results or a filtered-view page. So, I don't want it to be part of the filtering itself; but, I want it show up as associated data.

[zainforbjs]

@bennadel Thanks for raising this idea! I’ve looked into the suggestion around including non-selected computed SQL properties via something like an include mechanism. I’m going to explore this further on the Wheels side and assess the best approach to support it. I’ll update this thread once it is live.