# Ash Framework: Mention that aggregates can also point to resources (p. 79)

**URL:** <https://forum.devtalk.com/t/ash-framework-mention-that-aggregates-can-also-point-to-resources-p-79/212830>\
**Category:** PragProg Customers\
**Tags:** book-ash-framework\
**Created:** [29 August 2025 11:21 UTC](https://forum.devtalk.com/t/ash-framework-mention-that-aggregates-can-also-point-to-resources-p-79/212830 "2025-08-29T11:21:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![timpritlove](https://forum.devtalk.com/user_avatar/forum.devtalk.com/timpritlove/32/4715_2.png) [@timpritlove](https://forum.devtalk.com/u/timpritlove)\
**Post date:** [29 August 2025 11:21 UTC](https://forum.devtalk.com/t/ash-framework-mention-that-aggregates-can-also-point-to-resources-p-79/212830/1 "2025-08-29T11:21:53Z")

</div>

The last section in chapter 3 about aggregates mentions “„Aggregates perform some kind of calculation on records in a relationship“. However, when unterstand this change right, it might no longer be restricted to relationships but can be pointed directly at resources too:

> <https://github.com/ash-project/ash/pull/2240>
>
> the terminology here is a bit confusing, but aggregates were originally designed… over relationships. This allows to use a Resource, instead of a relationship.path in aggregates.
> 
> \# Contributor checklist
> 
> Leave anything that you believe does not apply unchecked.
> 
> \- \[\] I accept the \[AI Policy\](https://github.com/ash-project/.github/blob/main/AI\_POLICY.md), or AI was not used in the creation of this PR.
> \- \[\] Bug fixes include regression tests
> \- \[\] Chores
> \- \[\] Documentation changes
> \- \[\] Features include unit/acceptance tests
> \- \[\] Refactoring
> \- \[\] Update dependencies

I think this should at least be mentioned as it was part of the **[v3.5.35](https://github.com/ash-project/ash/releases/tag/v3.5.35) release.**

Also as aggregates completely replace the before constructed calculations one wonders what calculations are then for when they can be easier done with aggregates. The book should make a comment about this.

---

<div class="post-metadata">

**Author:** ![sevenseacat](https://forum.devtalk.com/user_avatar/forum.devtalk.com/sevenseacat/32/5897_2.png) [@sevenseacat](https://forum.devtalk.com/u/sevenseacat)\
**Post date:** [29 August 2025 12:09 UTC](https://forum.devtalk.com/t/ash-framework-mention-that-aggregates-can-also-point-to-resources-p-79/212830/2 "2025-08-29T12:09:49Z")

</div>

That’s true, aggregates can now be used for things other than relationships! That feature was added super recently, and is still having the tyres kicked (so to speak), and it’s a bit too late to update the book with this new info ☹

As for calculations, we do go into examples first on how they can be used for generally calculating things, like the `years_ago` that an album was released. We use them more in later chapters for things like the track number of an album, and policy checking who can manage album data!

---

<div class="post-metadata">

**Author:** ![timpritlove](https://forum.devtalk.com/user_avatar/forum.devtalk.com/timpritlove/32/4715_2.png) [@timpritlove](https://forum.devtalk.com/u/timpritlove)\
**Post date:** [30 August 2025 01:09 UTC](https://forum.devtalk.com/t/ash-framework-mention-that-aggregates-can-also-point-to-resources-p-79/212830/3 "2025-08-30T01:09:42Z")

</div>

I understand. Maybe consider leaving at least one “true” calculation in here that can’t or should not be converted to an aggregate. Otherwise this part seems kinda weird.