mirror of
https://github.com/ash-project/ash.git
synced 2024-09-20 21:43:02 +12:00
7bbd5a2162
When using `Ash.Query.set_result/2` to preempt the data layer action, we can end up in a position where the action has decided that some number of aggregates & calculations would be attached to the query. But its extremely unlikely that the data set with `set_result/2` would actually have handled loading/calculating things from the query, so we lazily load it after we get the data if that happens. |
||
---|---|---|
.. | ||
ash | ||
mix | ||
sat_solver | ||
ash.ex |